Qlik Talend Remote Engine 2.13.13 SSL Communication Issue with Talend Studio

david_lucas — Tue, 09 Sep 2025 05:02:34 GMT

After upgrading to Remote Engine 2.13.13, when enabling the option to execute a job from Studio on a remote engine, the process fails due to SSL and PKCS-related errors.

sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Resolution

SSL Configuration for Talend Studio to Connect with Remote Engine

Retain the Keystore and Truststore Passwords Generated During Installation
During the installation of Talend Remote Engine, SSL credentials are automatically generated. To retrieve the keystore password, execute the following command:
```
cat /opt/TalendRemoteEngine/bin/sysenv
```
and locate the line
```
TMC_ENGINE_JOB_SERVER_SSL_KEY_STORE_PASSWORD=<PASSWORD>
```
Required Keystore and Truststore Files
The following files are necessary for secure communication between Talend Studio and the Remote Engine:

/opt/TalendRemoteEngine/etc/keystores/jobserver-client-keystore.p12
/opt/TalendRemoteEngine/etc/keystores/jobserver-client-truststore.p12 (Truststore file added with RE 2.13.13)

Transfer these files to your Talend Studio workstation and store them in a dedicated folder.
Configure Talend Studio to Use SSL
Edit the Studio startup configuration file, depending on your operating system:
- For Linux (x86_64): studio/Talend-Studio-linux-gtk-x86_64.ini
- For ARM architecture: studio/Talend-Studio-gtk-aarch64.ini
- For Windows: Talend-Studio-win-x86_64.ini

Add the following JVM options to the configuration file, and adjust the file paths and password values accordingly:

    -Dorg.talend.remote.client.ssl.force=true
    -Dorg.talend.remote.client.ssl.keyStore=path_to_keystore/jobserver-client-keystore.p12
    -Dorg.talend.remote.client.ssl.keyStoreType=PKCS12
    -Dorg.talend.remote.client.ssl.keyStorePassword=<password_from_step_1>
    -Dorg.talend.remote.client.ssl.keyPassword=<password_from_step_1><
    -Dorg.talend.remote.client.ssl.trustStore=path_to_truststore/jobserver-client-truststore.p12
    -Dorg.talend.remote.client.ssl.trustStoreType=PKCS12
    -Dorg.talend.remote.client.ssl.trustStorePassword=<password_from_step_1>
    -Dorg.talend.remote.client.ssl.disablePeerTrust=false
    -Dorg.talend.remote.client.ssl.enabled.protocols=TLSv1.2,TLSv1.3

Cause

Talend Remote Engine enforces SSL communication by default, ensuring that all interactions with the engine are encrypted. If Studio does not have the appropriate certificates installed, it will be unable to establish a secure connection with the Remote Engine.

Environment

Re: Qlik Talend Remote Engine 2.13.13 SSL Communication Issue with Talend Studio

XRocq1696001865 — Thu, 07 May 2026 12:20:15 GMT

Hello for me it was another solution because this env variable does not exists and we dont need to change the .ini file of the studio.

The Talend RE v2.14.1 is on windows server 2019, and because the RE is a windows service wrapped, the password was in the cfg file of the Engine-wrapper.conf File

And on the Talend Studio R2026+ we configured that into the studio configuration menu > remote > SSL :

article Qlik Talend Remote Engine 2.13.13 SSL Communication Issue with Talend Studio in Official Support Articles

Qlik Talend Remote Engine 2.13.13 SSL Communication Issue with Talend Studio

Resolution

Cause

Environment

Re: Qlik Talend Remote Engine 2.13.13 SSL Communication Issue with Talend Studio