You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "German Eichberger (Jira)" <ji...@apache.org> on 2022/12/08 17:44:00 UTC
[jira] [Comment Edited] (CASSANDRA-12525) When adding new nodes to a cluster which has authentication enabled, we end up losing cassandra user's current crendentials and they get reverted back to default cassandra/cassandra crendetials
[ https://issues.apache.org/jira/browse/CASSANDRA-12525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644920#comment-17644920 ]
German Eichberger edited comment on CASSANDRA-12525 at 12/8/22 5:43 PM:
------------------------------------------------------------------------
[~smiklosovic] it's best practice after adding a second DC to run a (full) repair of the system_auth keyspace so with my patch this will effectively mitigate the issue for most people.
Also consider this scenario:
1. We bring up DC 1 in network A and change the cassandra user's password
2. We bring up DC 2 on network B - but due to some error the networks are not connected
3. We discover our error and connect network A and B so the DCs can see each other
In this case DC2 would not know that there is another DC (someone might just have misconfigured seed nodes) until the connection is established.To help with this scenario (other than my patch and repair) we would need some command line parameter so an operator can skip the initial role generation...
was (Author: JIRAUSER298386):
[~smiklosovic] it's best practice after adding a second DC to run a (full) repair of the system_auth keyspace so with my patch this will effectively mitigate the issue for most people.
Also consider this scenario:
1. We bring up DC 1 i network A and change the cassandra user's password
2. We bring up DC 2 on network B - but due to some error the networks are not connected
3. We discover our error and connect network A and B so the DCs can see each other
In this case DC2 would not know that there is another DC (someone might just have misconfigured seed nodes) until the connection is established.To help with this scenario (other than my patch and repair) we would need some command line parameter so an operator can skip the initial role generation...
> When adding new nodes to a cluster which has authentication enabled, we end up losing cassandra user's current crendentials and they get reverted back to default cassandra/cassandra crendetials
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-12525
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12525
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema, Local/Config
> Reporter: Atin Sood
> Assignee: German Eichberger
> Priority: Normal
> Fix For: 3.0.x, 3.11.x, 4.0.x, 4.1.x, 4.x
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Made the following observation:
> When adding new nodes to an existing C* cluster with authentication enabled we end up loosing password information about `cassandra` user.
> Initial Setup
> - Create a 5 node cluster with system_auth having RF=5 and NetworkTopologyStrategy
> - Enable PasswordAuthenticator on this cluster and update the password for 'cassandra' user to say 'password' via the alter query
> - Make sure you run nodetool repair on all the nodes
> Test case
> - Now go ahead and add 5 more nodes to this cluster.
> - Run nodetool repair on all the 10 nodes now
> - Decommission the original 5 nodes such that only the new 5 nodes are in the cluster now
> - Run cqlsh and try to connect to this cluster using old user name and password, cassandra/password
> I was unable to connect to the nodes with the original credentials and was only able to connect using the default cassandra/cassandra credentials
> From the conversation over IIRC
> `beobal: sood: that definitely shouldn't happen. The new nodes should only create the default superuser role if there are 0 roles currently defined (including that default one)`
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org