[
https://issues.apache.org/jira/browse/CASSANDRA-19957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17885374#comment-17885374
]
Stefan Miklosovic commented on CASSANDRA-19957:
-----------------------------------------------
anyway, how does this work in a scenario when I have 10-nodes cluster and 5
nodes are on one authenticator and 5 on the other? Then on client's side, they
would need to know what node they talk to in order to successfully connect to
that? That is very uncomfortable, isn't it?
I would do it like a node would be able to handle multiple authenticators at
the same time hence old clients can continue to work as they were used to and
new clients will be able to connect too. That way, once we bounce all clients,
we would just turn off the old way of authentication on server's side.
For now, we do not need to restart the node, sure, but the clients have a super
hard time to figure out what to do.
> Nodetool support to get and set the authenticator and authorizer
> ----------------------------------------------------------------
>
> Key: CASSANDRA-19957
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19957
> Project: Cassandra
> Issue Type: Improvement
> Components: Tool/nodetool
> Reporter: Ayushi Singh
> Assignee: Ayushi Singh
> Priority: Normal
>
> Add {{nodetool}} support in Apache Cassandra to dynamically get and set
> {{authorizer}} and {{authenticator}} configurations. Currently, changes
> require updating the config file and restarting Cassandra. The new commands
> will allow administrators to make updates on-the-fly without a server
> restart, improving flexibility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
