cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Zlatanov (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (CASSANDRA-547) authentication and authorization functions (stage 1)
Date Tue, 29 Dec 2009 20:59:29 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795146#action_12795146
] 

Ted Zlatanov edited comment on CASSANDRA-547 at 12/29/09 8:59 PM:
------------------------------------------------------------------

the latest auth patch, as suggested on cassandra-users, offers just one method: 

void login(String keyspace, Map<String, String> credentials)

The AllowAllAuthenticator, as before, simply allows any login and is intended to show the
default usage.

The patch is based on a 2009-12-29 checkout.  It also fixes the Thrift constructors by introducing
a ThriftGlue convenience factory class, which IMHO is the best way to keep source code concise
if the optional parameters can't be specified inline.

The ConsistencyLevel class is passed further down after the CassandraServer interface as an
int currently.  We may want to pass it as an enum everywhere instead.

Finally, I made a few style fixes, where return or continue were used in the if clause, so
the else was redundant.


      was (Author: tzz):
    the latest auth patch, as suggested on cassandra-users, offers just one method: 

void login(String keyspace, Map<String, String> credentials)

The AllowAllAuthenticator, as before, simply allows any login and is intended to show the
default usage.

The patch is based on a 2009-12-29 checkout.  It also fixes the Thrift constructors by introducing
a ThriftGlue convenience factory class, which IMHO is the best way to keep source code concise
if the optional parameters can't be specified inline.

Finally, I made a few style fixes, where return or continue were used in the if clause, so
the else was redundant.

  
> 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, libthrift-r893324.jar
>
>
> 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.


Mime
View raw message