Talend Remote Engine v2.12.2 is now generally available.
Signature with custom Java KeyStore
You can now strengthen trusted Job executions with support of your own JKS (Java KeyStore) signing key through the entire Job creation, deployment and execution lifecycle.
Talend Studio signs Jobs before they are deployed to Talend Cloud Management Console using Java Jar signing (https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#Signed_JAR_File).
Instead of using the default Studio signing key, it is possible to use a custom KeyStore for signature creation and validation.
To leverage this security strength, Remote Engine v2.12.0 and Studio v8.0 R2022-06 or their later versions are required. For further information, see Running trusted tasks with your custom signature.
|Job task timeout||Support for dynamic timeout of a Job task has been added to Remote Engine v2.12.0 and onwards.|
|TPOPS-3858||ActiveMQ has been upgraded to v5.16.5.|
|TPOPS-3926||Gson v2.8.9 is now used to avoid the CVE-2022-25647 vulnerability.|
|TPOPS-3821||The Remote Engine diagnostic tool talend-re-helper.sh has been updated to use shorter group ID.|
|TPOPS-4063||Remote Engine fails to start with a corruption that appears to be in the <RE_installation>/data/cls folder.|
|TPOPS-3756||Remote Engine is consuming high CPU ranging between 60% to 100%.|
Get started with Talend Remote Engine on Talend Remote Engine User Guide.