[
https://issues.apache.org/jira/browse/CASSANDRA-7653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15069466#comment-15069466
]
Sam Tunnicliffe commented on CASSANDRA-7653:
--------------------------------------------
bq. Is there any reason why we don't do this automatically?
Because, as you say, this is a potentially dangerous operation it's preferable
to have its execution controlled by an operator. Also, the schema change
provides a handy synchronisation point so we can have all nodes cut over to
using the new tables for live auth requests simultaneously. Coordinating that
otherwise is tricky.
> Add role based access control to Cassandra
> ------------------------------------------
>
> Key: CASSANDRA-7653
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7653
> Project: Cassandra
> Issue Type: Sub-task
> Components: CQL, Distributed Metadata
> Reporter: Mike Adamson
> Assignee: Sam Tunnicliffe
> Labels: docs-impacting, security
> Fix For: 2.2.0 beta 1
>
> Attachments: 7653.patch, CQLSmokeTest.java, cql_smoke_test.py
>
>
> 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)
