[
https://issues.apache.org/jira/browse/CASSANDRA-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795608#action_12795608
]
Eric Evans commented on CASSANDRA-547:
--------------------------------------
> If the latest patches are OK, I'll augment the auth patch with a working auth
> backend with static user
> credentials from the config file (user name and password specified in the
> configuration per keyspace).
> That >will be all for stage1 and I'll go on to stage2: the LDAP and other
> backends we discussed.
Can we avoid putting anything other than the back-end in storage-conf.xml? If
the back-ends are to be pluggable, then trying to come up a standard set of
directives that will cover them all is going to be a lot of Fail.
I'd rather see each back-end handle configuration on its own. For example, a
static credential back-end could look in -Dstorage-config for a
passwd.properties file or something. An LDAP back-end could look for an
ldap.conf, etc.
> 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, CASSANDRA-547-thrift.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.
