Was this page helpful?
Caution
You're viewing documentation for an unstable version of ScyllaDB Enterprise. Switch to the latest stable version.
Authentication is the process where login accounts and their passwords are verified, and the user is allowed access to the database. Authentication is done internally within ScyllaDB and is not done with a third party. Users and passwords are created with roles using a CREATE ROLE statement. Refer to Grant Authorization CQL Reference for details.
The procedure described below enables Authentication on the ScyllaDB servers. It is intended to be used when you do not have applications running with ScyllaDB/Cassandra drivers.
Warning
Once you enable authentication, all clients (such as applications using ScyllaDB/Apache Cassandra drivers) will stop working until they are updated or reconfigured to work with authentication.
If this downtime is not an option, you can follow the instructions in Enable and Disable Authentication Without Downtime, which using a transient state, allows clients to work with or without Authentication at the same time. In this state, you can update the clients (application using ScyllaDB/Apache Cassandra drivers) one at the time. Once all the clients are using Authentication, you can enforce Authentication on all ScyllaDB nodes as well.
For each ScyllaDB node in the cluster, edit the /etc/scylla/scylla.yaml file to change the authenticator parameter from AllowAllAuthenticator to PasswordAuthenticator.
authenticator: PasswordAuthenticator
Restart ScyllaDB.
sudo systemctl restart scylla-serverdocker exec -it some-scylla supervisorctl restart scylla(without restarting some-scylla container)
Start cqlsh with the default superuser username and password.
cqlsh -u cassandra -p cassandra
Note
Before proceeding to the next step, we recommend creating a custom superuser to improve security. See Creating a Custom Superuser for instructions.
If you want to create users and roles, continue to Enable Authorization.
Was this page helpful?