[CASSANDRA-10209] Missing role manager in cassandra.yaml causes unexpected behaviour

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 2.2.2, 3.0.0 rc1
• Component/s: Local/Config
• Severity: Low
• Assignee: Sam Tunnicliffe
• Reporter: Sam Tunnicliffe

Authors

Sam Tunnicliffe

Reviewers

Jonathan Ellis

• Created: 27/Aug/15 19:19
• Updated: 16/Apr/19 09:30
• Resolved: 08/Sep/15 09:47

Description

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

role_manager: CassandraRoleManager