[
https://issues.apache.org/jira/browse/CASSANDRA-5423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13622528#comment-13622528
]
Jonathan Ellis commented on CASSANDRA-5423:
-------------------------------------------
Where does that happen on e.g. the insert path? Throwing NPE doesn't count. :)
(ensureHasAccess doesn't work either for AllowAll... Even for other
authenticators, I'm not sure we want to return "no access" instead of "doesn't
exist.")
> PasswordAuthenticator is incompatible with various Cassandra clients
> --------------------------------------------------------------------
>
> Key: CASSANDRA-5423
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5423
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.3
> Reporter: Sven Delmas
> Assignee: Aleksey Yeschenko
> Priority: Minor
> Labels: security
> Fix For: 1.2.4
>
> Attachments: 5423.txt
>
>
> Evidently with the old authenticator it was allowed to set keyspace, and then
> login. With the org.apache.cassandra.auth.PasswordAuthenticator you have to
> login and then setkeyspace
> For backwards compatibility it would be good to allow setting before login,
> and perform the actual operation/validation later after the login.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
