Single Tenant Operation

[Table of Contents](https://github.com/dell-oss/Doradus/wiki/Doradus Administration: Table-of-Contents) | [Previous](https://github.com/dell-oss/Doradus/wiki/Tenant Mapping to Cassandra) | [Next](https://github.com/dell-oss/Doradus/wiki/Multi-Tenant Operation)
[Multi-Tenant Configuration](https://github.com/dell-oss/Doradus/wiki/Multi-Tenant Configuration): Single Tenant Operation

---

By default, Doradus operates in *single-tenant* mode, which means all applications are created in a single keyspace with a default name. Single-tenant mode is affected primarily by two doradus.yaml file options:

multitenant_mode: false
keyspace: 'Doradus'

When multitenant_mode is false, all applications are stored in the default keyspace defined by the keyspace option.

Single-tenant mode does not require security to be enforced within Cassandra. However, you can configure Cassandra to enforce user/password authentication by setting the following options in each Cassandra node’s cassandra.yaml:

authenticator: PasswordAuthenticator
authorizer: CassandraAuthorizer

When Cassandra first starts with these options, it creates a default super user account with the user ID and password cassandra/Cassandra. You should change the super user ID and/or password to something more secure. Doradus must use a super user account for access, hence set the following doradus.yaml options to a valid super user account:

dbuser: cassandra
dbpassword: cassandra

You can also pass these options into Doradus as runtime as arguments "-dbuser xxx -dbpassword yyy".