Encrypting secrets stored in JobServer configuration file

You can enable encryption of password properties in the Talend JobServer configuration file.

By default, this encryption feature is disabled. To enable it, do the following.

Procedure

Go to the directory <root>/conf/, where <root> is the Talend JobServer path, and open the aeskey.dat file to edit it.
The aeskey.dat file contains a Base64 encoded secret in the following format:
```
aes.key=<BASE64 encoded AES key>
```
Generate your own encryption secret.
For example, using the command:
```
openssl rand 32 | base64
```
Replace the secret in <root>/conf/aeskey.dat with your own one.
Open the <root>/conf/TalendJobServer.properties file to edit it.

Set the following parameter to true.

org.talend.remote.jobserver.encrypt=true

Save your changes and restart the Talend JobServer so that the configuration takes effect.

Results

On start of Talend JobServer, this setting will cause the following passwords to be encrypted using the Base64 encoded secret in property aes.key inside <root>/conf/aeskey.dat:

org.talend.jmxmp.ssl.keyStorePassword
org.talend.jmxmp.ssl.trustStorePassword
org.talend.remote.server.ssl.keyStorePassword
org.talend.remote.server.ssl.trustStorePassword

To modify the location and name of the key file, set the encryption.keys.file system property in the Talend JobServer start script start_rs.sh.

Note: For Talend ESB, you need to set org.talend.remote.jobserver.encrypt=true in <KARAF_HOME>/etc/org.talend.remote.jobserver.server.cfg and store your secret inside <KARAF_HOME>/etc/aeskey.dat. To modify location and the name of the key file, set the encryption.keys.file system property in the start script trun.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here