[
https://issues.apache.org/jira/browse/IGNITE-12851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergei Ryzhov updated IGNITE-12851:
-----------------------------------
Description:
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.
was:
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.
I suggest ADMIN_CACHE mark @Deprecated
and replace it in the GridRestProcessor with CACHE_CREATE / CACHE_DESTROY
while maintaining backward compatibility for ADMIN_CACHE.
This will allow us to remove ADMIN_CACHE in the future.
> Inconsistent 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
>
> 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)
