[jira] [Resolved] (CASSANDRA-10209) Missing role manager in cassandra.yaml causes unexpected behaviour

["Sam Tunnicliffe (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-10209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sam Tunnicliffe resolved CASSANDRA-10209.
-----------------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 2.2.x)
                   2.2.2

> Missing role manager in cassandra.yaml causes unexpected behaviour
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-10209
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10209
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Minor
>             Fix For: 3.0.0 rc1, 2.2.2
>
>
> On upgrading to 2.2+, if the new {{role_manager}} option is not added to {{cassandra.yaml}}, an instance of the default {{CassandraRoleManager}} is created during initialization of {{DatabaseDescriptor}}. This is a problem as the set of role options supported by {{CRM}} depends on the configured {{IAuthenticator}}, which at that point in time is always {{AllowAllAuthenticator}}.
> This StackOverflow post describes the problem; the configured authenticator is {{PasswordAuthenticator}}, the role manager should allow roles to be created using the {{PASSWORD}} option, but it does not.
> http://stackoverflow.com/questions/31820914/in-cassandra-2-2-unable-to-create-role-containing-password
> The simple workaround is to ensure that yaml contains the role manager option
> {code}
> role_manager: CassandraRoleManager
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)