You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Sergei Ryzhov (Jira)" <ji...@apache.org> on 2020/04/01 10:37:00 UTC

[jira] [Updated] (IGNITE-12851) Inconsistent CACHE_CREATE/DESTROY authorization logic API IgniteClient and REST

     [ https://issues.apache.org/jira/browse/IGNITE-12851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergei Ryzhov updated IGNITE-12851:
-----------------------------------
    Summary: Inconsistent CACHE_CREATE/DESTROY authorization logic API IgniteClient and REST  (was: Inconsistent API IgniteClient and REST)

> Inconsistent CACHE_CREATE/DESTROY authorization logic API IgniteClient and REST
> -------------------------------------------------------------------------------
>
>                 Key: IGNITE-12851
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12851
>             Project: Ignite
>          Issue Type: Wish
>          Components: security
>    Affects Versions: 2.8
>            Reporter: Sergei Ryzhov
>            Assignee: Sergei Ryzhov
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Now the work of permissions for API IgniteClient and REST is different.
> To create/delete a cache:
> IgniteClient authorises CACHE_CREATE/CACHE_DESTROY.(GridCacheProcessor#authorizeCacheCreate, authorizeCacheDestroy)
> REST authorises ADMIN_CACHE.(GridRestProcessor#authorize)
> I think this is inconsistent.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)