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 08:57:00 UTC
[jira] [Created] (IGNITE-12851) Inconsistent API IgniteClient and
REST
Sergei Ryzhov created IGNITE-12851:
--------------------------------------
Summary: 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
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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)