Steps for new deployment
Here are high-level steps for implementing HCD Unified Authentication in a new deployment.
|
To implement authentication and authorization in a pre-established HCD environment, additional precautions and steps are required. See Steps for production environments. |
Configure HCD Unified Authentication
-
Ensure that required data for logins and permission management are accessible and in all datacenters. See Configure the security keyspaces replication factors.
-
Configure the system settings. See Enable HCD Unified Authentication.
-
Configuring authentication and authorization methods (schemes):
-
Internally stored passwords. No additional configuration is required create roles with passwords as described in Set up logins and users.
-
External LDAP. See Define an LDAP scheme.
-
Kerberos.
-
-
Configure JMX authentication: Requires changes to the
cassandra-env.shfornodetoolandhcdtoolto run against an authentication enabled cluster.The location of the
cassandra-env.shfile depends on the type of installation:-
Package installations:
/etc/hcd/cassandra/cassandra-env.sh -
Tarball installations:
<installation_location>/resources/cassandra/conf/cassandra-env.sh
-
-
Restart HCD. See Starting and stopping HCD.
Nodes are vulnerable to malicious activity following the restart. Anybody can access the system using the default cassandra account with password cassandra. DataStax recommends isolating the cluster until after disabling the cassandra account.
-
Set up your own root account and disable or drop the default, cassandra account. See Add a superuser login.
Using the default cassandra account may impact performance, because all requests including login execute with consistency level QUORUM. DataStax recommends only using this account to create your root account.
-
Create roles that map to users in the configured schemes and grant permission to allow users access to database resources, such as keyspaces and tables. See Set up logins and users.
-
Use the latest DataStax certified drivers in all applications connecting to HCD Unified Authentication-enabled transactional nodes. HCD drivers support all the features of the Cassandra drivers and provide additional support for multiple authentication methods as well as externally managed roles assignment. See DataStax drivers.
-
Spark component limitations: HCD provides internal authentication support for connecting Spark to HCD transactional nodes, not for authenticating between Spark components.
-
Next steps
After enabling authentication and authorization, run tools by supplying credentials:
