[
https://issues.apache.org/jira/browse/CASSANDRA-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784230#action_12784230
]
Ted Zlatanov commented on CASSANDRA-547:
----------------------------------------
Consider this simply a very early prototype.
The API is simple. Three functions are available:
void login(Map<String, String> credentials) throws AuthenticationException
void setKeyspace(String keyspace) throws AuthorizationException
String getKeyspace()
There is an AllowAllAuthenticator backend that implements the default (approve
all) policy.
For backwards compatibility, the current API will still work. Whenever a
function that takes a keyspace argument is called, it will call setKeyspace()
on the auth backend, ignoring any exceptions (to keep the current API the same
as far as exceptions). In a later API revision, this will be changed in favor
of just setting the keyspace 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
> Affects Versions: 0.5
> Reporter: Ted Zlatanov
> Assignee: Ted Zlatanov
> Attachments: 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.
