[
https://issues.apache.org/jira/browse/CASSANDRA-7653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14163201#comment-14163201
]
Hans van der Linde commented on CASSANDRA-7653:
-----------------------------------------------
The RBAC feature is something which is on our list. I work at a financial
company and in order to comply to the security guidelines at financial
companies, we want to have a more fine grained granularity on Cassandra
user(s).
For example a Cassandra user which can only read data uses SELECT, that's a
tick in the box.
But how can we setup a Cassandra user which can only do INSERT/UPDATE without
having the permission to do run the cql statement DELETE and/or TRUNCATE?
Can we add this option also into this jira?
> Add role based access control to Cassandra
> ------------------------------------------
>
> Key: CASSANDRA-7653
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7653
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Mike Adamson
> Assignee: Mike Adamson
> Fix For: 3.0
>
> Attachments: 7653.patch
>
>
> The current authentication model supports granting permissions to individual
> users. While this is OK for small or medium organizations wanting to
> implement authorization, it does not work well in large organizations because
> of the overhead of having to maintain the permissions for each user.
> Introducing roles into the authentication model would allow sets of
> permissions to be controlled in one place as a role and then the role granted
> to users. Roles should also be able to be granted to other roles to allow
> hierarchical sets of permissions to be built up.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
