Using data encryption ensures that all future operations written to the local backends, LDAP changelog, and replication database are protected from unauthenticated sources.
Enabling data encryption after setting up the server can result in unencrypted data being stored in local DB backends, the LDAP changelog, and the replication database. You should export all local DB backends to LDIF and re-import the data after enabling encryption to ensure that all data is properly encrypted. This will also ensure that all indexes are encrypted.
To enable data encryption:
Global property | Configuration description |
---|---|
|
Indicates whether data encryption is enabled in the server:
|
|
Indicates which cipher stream provider should be used to protect the contents of the encryption settings database. By default, an instance of the file-based cipher stream provider is used to encrypt the database with a key generated by a passphrase read from a specified file. |
|
Indicates whether the server should encrypt backups by default:
|
|
Specifies the unique identifier of the encryption settings definition to use in generating the encryption key:
|
|
Indicates whether the server should encrypt LDIF exports by default:
|
|
Indicates whether to automatically compress LDIF exports that are encrypted. If set to |
$ bin/dsconfig set-global-configuration-prop --set encrypt-data:true