Configure HCD Unified Authentication in a live cluster

To implement HCD Unified Authentication in an existing deployment (a live cluster) without downtime or interrupted access, use transitional modes to temporarily support applications and users that don’t have accounts:

  1. Update all applications to provide credentials and ensure that they use the latest version of a supported Apache Cassandra driver.

    When using authentication.transitional_mode, you can provide a blank username and password to log in with the anonymous role.

    When authentication and authorization are disabled, the credentials portion of the connection request is ignored. After authentication is enabled all connections must provide credentials.

  2. Change the replication factor for the security keyspaces.

  3. Run a full repair of the system_auth keyspace.

  4. On each node, enable authentication and authorization in transitional mode:

    • Set authentication.transitional_mode to permissive in the cassandra.yaml file.

    • Set authorization.transitional_mode to normal in the cassandra.yaml file.

    For more information, see Enable HCD Unified Authentication.

  5. Enable logging so you can verify that applications are authenticating successfully.

  6. Enable JMX authentication.

  7. Perform a rolling restart of all nodes in the cluster.

    Nodes are vulnerable to malicious activity following this restart. Anybody can access the system using the default cassandra account with password cassandra. DataStax recommends isolating the cluster until you disable the cassandra account.

    Additionally, using the default cassandra account can impact performance because all requests, including login, execute with consistency level QUORUM. DataStax recommends using the cassandra account only to create a new superuser (root) account.

  8. After all nodes restart, use cqlsh to replace the cassandra default account with a superuser login.

  9. Switch to the new superuser account, and then configure roles and assign permissions.

  10. Disable or drop the default cassandra account.

  11. Monitor audit logs to verify that all applications can access nodes and have the permissions required to execute requests.

  12. In the cassandra.yaml file, set authenticator.parameters.enabled to true, and then configure specific authentication schemes, such as LDAP.

  13. Perform a rolling restart of the cluster.

Was this helpful?

Give Feedback

How can we improve the documentation?

© Copyright IBM Corporation 2026 | Privacy policy | Terms of use Manage Privacy Choices

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries. Kubernetes is the registered trademark of the Linux Foundation.

General Inquiries: Contact IBM