Encrypting Configuration File Properties

Configure DataStax Enterprise (DSE) to use a local encryption key to decrypt properties in the configuration file. Use passwords encrypted with the local key.

dse.yaml LDAP values:
```
ldap_options.search_password
ldap_options.truststore_password
```
Use plain text for the KMIP keystore and truststore passwords.
cassandra.yaml SSL values:
```
server_encryption_options.keystore_password
server_encryption_options.truststore_password
client_encryption_options.keystore_password
client_encryption_options.truststore_password
```
1. Complete the key setup described in Setting up local encryption keys.
  
  When using a local encryption key file, set the location system_key_directory, and ensure that the key file is owned by the account running DSE.
2. For each property, replace plain text passwords with encrypted passwords returned by running the dsetool encryptconfigvalue command:
  1. Encrypt the password:
    
    dsetool encryptconfigvalue
    
    Result
    
    Using system key system_key Enter value to encrypt: Enter again to confirm: Your encrypted value is: +Vj5oHCR/jqfA+OJE2m8zA==
  2. Replace the old value with the new value in the configuration file. For example, if the old value was the SSL truststore password in the cassandra.yaml file:
    
    truststore_password: +Vj5oHCR/jqfA+OJE2m8zA==
    
    After the configuration file property encryption is enabled, DSE startup fails if any of the protected properties are not encrypted.
3. Locate the dse.yaml and cassandra.yaml configuration files. The location of these files depends on the type of installation:
  
  dse.yaml
Package installations: /etc/dse/dse.yaml
Tarball installations: <installation_location>/resources/dse/conf/dse.yaml

cassandra.yaml
Package installations: /etc/dse/cassandra/cassandra.yaml
Tarball installations: <installation_location>/resources/cassandra/conf/cassandra.yaml
1. In dse.yaml, enable configuration file property encryption:
  1. Set config_encryption_active to true:
    
    config_encryption_active: true
    
    When set to true, the configuration values must be encrypted or commented out.
    
    Lifecycle Manager (LCM) isn’t compatible when config_encryption_active is true in DSE and OpsCenter. See Lifecycle Manager configuration known issues and limitations.
  2. Set the local key encryption filename:
    
    config_encryption_key_name: <key_filename>
2. Update the dse.yaml and cassandra.yaml on all nodes in the cluster.
3. Set up encryption for system resources, see Encrypting system resources.
4. Perform a rolling restart.

Encrypting Configuration File Properties

Was this helpful?

Give Feedback