ApiExecutor allows use of individual truststore and keystore

Current Situation

The APIExecutor Java class used by JITL Jobs requires the name of the truststore to be specified in order to determine which truststore to use from the list of truststores in the Agent's private.conf configuration file.

• JITL jobs do not specify the truststore parameter.
• The APIExecutor therefore falls back to use of the default name https-truststore.p12 and does not allow use of a different name or path of the truststore.

Desired Behavior

The APIExecutor should use all truststores from the related configuration in the private.conf file. The JITL jobs do not specify the truststore and keystore to be used.

Additionally, the ApiExecutor should support custom jobs that do not make use of the private.conf file, but use different truststores and keystore paths.

Therefore two methods should be introduced to configure the path to the truststore, the truststore type and password. The same applies to a keystore with an optional password for the private key: 

• setTruststore(String path, String type, String storePwd)
• setKeystore(String path, String type, String storePwd, String keyPwd)

Patches

• 2.5.5
  •  https://download.sos-berlin.com/patches/2.5.5-patch/js7_agent.2.5.5-PATCH.JITL-725.jar [sha256] [sig] [tsr]
• 2.6.2
  •  https://download.sos-berlin.com/patches/2.6.2-patch/js7_agent.2.6.2-PATCH.JITL-725.jar [sha256] [sig] [tsr]

These patches can also be applied to any 2.5.x version and any 2.6.x version respectively.