cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yuki Morishita (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4490) Improve IAuthority interface by introducing fine-grained access permissions and grant/revoke commands.
Date Thu, 06 Sep 2012 15:23:07 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449732#comment-13449732
] 

Yuki Morishita commented on CASSANDRA-4490:
-------------------------------------------

Hmm, if LIST GRANTS command is expected to return list of Permission, then I think you should
change method signature of listPermissions to return List<Permission> or some other
Collection<Permission>. It would describe API more precisely.
                
> Improve IAuthority interface by introducing fine-grained access permissions and grant/revoke
commands.
> ------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-4490
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4490
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Pavel Yaskevich
>            Assignee: Pavel Yaskevich
>            Priority: Minor
>             Fix For: 1.1.6
>
>         Attachments: 4490-v3.txt, CASSANDRA-4490.patch, CASSANDRA-4490-v2.patch
>
>
> In order to improve IAuthority interface I propose to add the following new permissions:
USE, SELECT, CREATE, ALTER, DROP, UPDATE, DELETE, ALL, NONE. And the following new commands
to the CQL 3.0 which would give users possibility (with appropriate implementation) to dynamically
change user's rights to access system objects:
> GRANT  <permission> ON <resource> TO <user> [WITH GRANT OPTION];
> REVOKE <permission> ON <resource> FROM <user_name>;
> LIST GRANTS FOR <user>; // Not 'SHOW' because it's reserved for cqlsh for commands
like 'show cluster'
> where <resource> is Keyspace or ColumnFamily (initially, but extendable to indexes
or configration options in the future), and <permission> is listed above.
> To keep the system backward compatible with old authorization interface implementations
Permission class would include the mappings of the new to old 
> permissions:
> READ  -> USE, SELECT
> WRITE -> USE, CREATE, ALTER, DROP, UPDATE, DELETE

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message