Third-party components in Integration Server such as databases and LDAP use JSSE to make outbound calls to external servers. In these cases, the third-party component uses JSSE directly to make the call. The third-party component does not use the default SSL settings configured for Integration Server. Instead, when a third-party component uses secure socket layers (SSL) with external servers, the Integration Server JVM uses the javax.net.ssl properties in the JVM for creating the SSL Context for the SSL handshake.

You can set the keystore location, truststore location, and password information using the javax.net.ssl properties for the JVM. However, these properties take String values which can result in storing password information in plain text somewhere on the file system. This represents a security vulnerability.

To address this security issue, Integration Server provides a way to specify the keystore and truststore locations and passwords for the JVM in a way in which the passwords are not stored in plain text. Specifically, Integration Server Administrator provides the JVM Keystore Alias and JVM Truststore Alias fields on the Security > Certificates page. Use these fields to specify the keystore and truststore aliases that the JVM uses establish the default SSL context. At start up, Integration Server sets the javax.net.ssl properties by obtaining the store locations and passwords from the aliases.