[
https://issues.apache.org/jira/browse/CASSANDRA-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802044#action_12802044
]
Eric Evans commented on CASSANDRA-547:
--------------------------------------
Ok, this has been committed, with some changes.
This changeset breaks client compatibility and the current plan is to
fast-track an 0.6 release with no-breaking changes. As a result, the biggest
change I made was to special case AllowAllowAuthenticator so that it is not
required to call login(). This is strictly temporary until we have an 0.6
branch, at which point we can reverse this in trunk.
(The other changes should be self-explanatory)
I believe there is more to do here, but I'm going to close this ticket. Let's
open new issues for each additional item and track them separately.
> 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
> Fix For: 0.7
>
> Attachments: CASSANDRA-547-auth.patch,
> CASSANDRA-547-auth2-4eevans.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.
