[
https://issues.apache.org/jira/browse/CASSANDRA-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797181#action_12797181
]
Eric Evans commented on CASSANDRA-547:
--------------------------------------
> 2) a common way to specify authorizations (see my earlier comment on a
> proposed scheme)
I'm not a fan of this. If it's being left out of storage-conf.xml because it
isn't reasonable to define this upfront for all possible back-ends (and I still
believe it is), then a separate file only moves the problem. This should really
be left up to the back-end, and if there is a good standard, there is nothing
to stop it from emerging naturally.
> authentication and authorization functions (stage 1)
> ----------------------------------------------------
>
> Key: CASSANDRA-547
> URL: https://issues.apache.org/jira/browse/CASSANDRA-547
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Ted Zlatanov
> Assignee: Ted Zlatanov
> Attachments: CASSANDRA-547-auth.patch
>
>
> Add functions to login() and setKeyspace(). Check against
> authentication+authorization backends whether those calls should succeed or
> fail.
> Create file-based and LDAP backends to implement authentication and
> authorization.
> Create AllowAll backend to allow all access.
> Add configuration stanza to specify the auth backend.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
