[
https://issues.apache.org/jira/browse/CASSANDRA-7216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001606#comment-14001606
]
Aleksey Yeschenko commented on CASSANDRA-7216:
----------------------------------------------
[~odpeer] Or you could go further. Pre-create the keyspace in the authenticator
itself, and then grant all you need just on the keyspace itself, so that the
top-level resource won't have to be involved. Because as it is right now, users
will be able to create tables in every other keyspace as well.
> Restricted superuser account request
> ------------------------------------
>
> Key: CASSANDRA-7216
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7216
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Oded Peer
> Assignee: Dave Brosius
> Priority: Minor
> Fix For: 3.0
>
> Attachments: 7216.txt
>
>
> I am developing a multi-tenant service.
> Every tenant has its own user, keyspace and can access only his keyspace.
> As new tenants are provisioned there is a need to create new users and
> keyspaces.
> Only a superuser can issue CREATE USER requests, so we must have a super user
> account in the system. On the other hand super users have access to all the
> keyspaces, which poses a security risk.
> For tenant provisioning I would like to have a restricted account which can
> only create new users, without read access to keyspaces.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
