/
Encrypt sensible configuration data in repository.cfg file

Encrypt sensible configuration data in repository.cfg file

Using the keystore service, sensible configuration information can be stored savely as a secret in the keystore vault file.

For more information, please see Set up a KeyStore (tC) .

 

Example:

To import a secret referenced by alias MySecret" (you may want to use a different alias name) into the keystore value file execute this command:

keytool -importpass -storetype pkcs12 -alias MySecret -keystore <Keystorename> -storepass <keystorepassword>

Reference this secret in repository.cfg file like this:

repo1.protocolservice.elastic.authentication.credentials:elasticuser,MySecret

 

Related content

Encryption Service
Encryption Service
More like this
Location of the repository.cfg file
Location of the repository.cfg file
Read with this
Config Data Service - Type filesystem (tC)
Config Data Service - Type filesystem (tC)
More like this
Deployment as WAR / in Tomcat (tC)
Deployment as WAR / in Tomcat (tC)
Read with this
KeyStore Type - pkcs12_storage (tC)
KeyStore Type - pkcs12_storage (tC)
More like this
Configuration of logging framework in container deployment
Configuration of logging framework in container deployment
Read with this