[
https://issues.apache.org/jira/browse/CASSANDRA-4490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13452614#comment-13452614
]
Hudson commented on CASSANDRA-4490:
-----------------------------------
Integrated in Cassandra #2084 (See
[https://builds.apache.org/job/Cassandra/2084/])
changes related to CASSANDRA-4490 merge (Revision
804dd099121f4b1b16344526e25c45c913bd5082)
small fix in permission checking in ClientState, related to CASSANDRA-4490
(Revision e172a9b735ef8f99cf45ba86c9850943829d14fb)
Result = ABORTED
xedin :
Files :
* src/java/org/apache/cassandra/cql3/statements/CreateKeyspaceStatement.java
* src/java/org/apache/cassandra/cql3/statements/CreateColumnFamilyStatement.java
* src/java/org/apache/cassandra/cql/QueryProcessor.java
* src/java/org/apache/cassandra/cql3/statements/DropKeyspaceStatement.java
xedin :
Files :
* src/java/org/apache/cassandra/service/ClientState.java
> 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
