cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5423) PasswordAuthenticator is incompatible with various Cassandra clients
Date Thu, 04 Apr 2013 19:20:15 GMT

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

Aleksey Yeschenko commented on CASSANDRA-5423:
----------------------------------------------

We do. Look at 'find usages' of ThriftValidation validateTable and both validateColumnFamily
methods (that do in turn call validateTable).

CASSANDRA-5358 is orthogonal (and IMO should just be resolved with 'not a problem').
                
> 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

Mime
View raw message