Enabling the SSL encryption in Talend Runtime

The execution servers provided by Qlik allows you to encrypt data prior to transmission via an existing SSL Keystore.

Procedure

Go to the etc directory and open the org.talend.remote.jobserver.server.cfg file to edit it. Use the following parameters as a template:

# ESB Runtime server SSL configuration
org.talend.remote.server.ssl.keyStore=${keystoreFolder}/runtime-jobserver-server-keystore.p12
org.talend.remote.server.ssl.keyStoreType=PKCS12
org.talend.remote.server.ssl.keyStorePassword=${sslServerKeystorePassword}
org.talend.remote.server.ssl.keyPassword=${sslServerKeystorePassword}
org.talend.remote.server.ssl.trustStore=${keystoreFolder}/runtime-jobserver-server-truststore.p12
org.talend.remote.server.ssl.trustStoreType=PKCS12
org.talend.remote.server.ssl.trustStorePassword=${sslServerTruststorePassword}
org.talend.remote.server.ssl.enabled.protocols=TLSv1.2,TLSv1.3

In theorg.talend.remote.jobserver.server.TalendJobServer.USE_SSL=false line, replace false with true.
The next time you launch your execution server, the SSL protocol will be used to secure the communication between servers and clients.
In Talend Administration Center, select the Use https check box to enable the encryption.

In <tac-installation>/apache-tomcat/bin/setenv.bat, extend the JAVA_OPTS specification with the following settings:

-Dorg.talend.remote.client.ssl.keyStore=${keystoreFolder}/runtime-client-keystore.p12
                  -Dorg.talend.remote.client.ssl.keyStorePassword=${sslClientKeystorePassword}
                  -Dorg.talend.remote.client.ssl.trustStore=${keystoreFolder}/runtime-client-truststore.p12
                  -Dorg.talend.remote.client.ssl.trustStorePassword=${sslClientTruststorePassword}
                  -Dorg.talend.remote.client.ssl.enabled.protocols=TLSv1.2,TLSv1.3

Write this line as follows:

export JAVA_OPTS="$JAVA_OPTS -Xmx2048m -Dfile.encoding=UTF-8 -Dorg.talend.remote.client.ssl.keyStore=..."

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