Skip to main content Skip to complementary content

Activating user authentication for file upload on Talend JobServer

Activate user authentication to restrict the permission of uploading files to Talend JobServer to authenticated users only.

Before you begin

Backward compatibility: Existing configurations for Talend Studio, Talend Administration Center, and Talend JobServer remain compatible after applying these patches.

Procedure

  1. Stop Talend Studio and enable this feature in Talend Studio.
    Open the <Studio_installation>/Talend-Studio-*.ini file, add the following line:
    -Dorg.talend.remote.jobserver.client.old=false
  2. Stop Talend Administration Center and enable this feature in it.
    Open the TAC_installation/apache-tomcat/bin/setenv.sh or the TAC_installation/apache-tomcat/bin/setenv.bat file, add the following system property to the JAVA_OPTS variable.
    org.talend.remote.jobserver.client.old
    This should make the JAVA_OPTS line look like:
    export JAVA_OPTS="$JAVA_OPTS -Xmx4096m -Dfile.encoding=UTF-8 -Dorg.talend.remote.jobserver.client.old=false"
  3. Restart Talend Studio and Talend Administration Center.

    The servers may report exceptions because Talend Studio and Talend Administration Center attempt to use the new protocol before reverting to the legacy protocol. However, all Jobs continue to run successfully.

  4. Stop your Talend JobServer and enable this feature on this server side.
    Open the <JobServer_installation>/conf/TalendJobServer.properties file to add the following line:
    org.talend.remote.jobserver.commons.config.JobServerConfiguration.FILESERVER_AUTHORIZATION=true
  5. Restart your Talend JobServer.

    After approximately one hour, all clients such as Talend Studio and Talend Administration Center recognize and apply the new user authentication for file uploading.

    If you exclude any Talend JobServer instances from the patch, they continue to function without this authentication protection. Consequently, clients report hourly exceptions when attempting to locate the new protocol before reverting to the legacy version. All Jobs continue to run successfully despite these exceptions.

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!