[
https://issues.apache.org/jira/browse/CASSANDRA-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797236#action_12797236
]
Ted Zlatanov edited comment on CASSANDRA-547 at 1/6/10 6:47 PM:
----------------------------------------------------------------
updated patch for eevans comments:
I think abstracting the credentials inside the AuthenticationRequest makes
sense because it's very likely authentication and authorization will evolve
over time. Limiting them to just a string-string map is going to bite us
eventually. I'd like to leave this as it is.
I changed to RuntimeException where it made sense (missing MD5 algorithm is
still announced to the user since it's requested by them).
I removed the keyspace_ member altogether from AllowAllAuthenticator. It was
not used anyhow.
Everything is named *Authenticator now (save the bytes!)
was (Author: tzz):
updated patch for eevans comments
> 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.
