[
https://issues.apache.org/jira/browse/CASSANDRA-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Zlatanov updated CASSANDRA-547:
-----------------------------------
Attachment: CASSANDRA-547-auth2-4eevans.patch
Fixed the issues reported by eevans:
- remove setAuthenticator
- provide commented example of using the AllowAllAuthenticator in the
storage-conf.xml file
- provide commented conf/{passwd,authorization}.properties
- rename CassandraServer.login_done to CassandraServer.loginDone
All this is in a second patch as requested.
Regarding the null == X to X == null, I think the former is better because it
makes it impossible to assign null accidentally. In Java this doesn't happen
as much but it can (if you're testing if a Boolean is null and forget the
second '='). It's a good habit that has no significance to the compiler and I
really doubt would confuse the reader. If you still want it in the X==null
format, go ahead and make that change or I can produce the corresponding
trivial patch.
> 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-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.
