cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (CASSANDRA-7216) Restricted superuser account request
Date Tue, 03 Jun 2014 18:02:02 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-7216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aleksey Yeschenko updated CASSANDRA-7216:
-----------------------------------------

    Comment: was deleted

(was: [~dbrosius] I don't have an issue with the original patch, it LGTM, except, well, that
it's not enough on its own.

Having a USERADMIN would let you do *most* things with users, but doesn't cover the initial
creation. A )

> 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-POC.txt, 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)

Mime
View raw message