Integration Server 10.3 | Integration Server Administrator's Guide | Configuring Ports | Adding a Security Provider
 
Adding a Security Provider
If you want to add an HTTPS or FTPS port with a listener that will use a private key and certificate chain residing in a keystore and the keystore is managed by a non standard Security Provider, you may need to add that Security Provider to Integration Server Administrator.
When specifying keystore information in the HTTPS or FTPS port information screen, a non standard Security Provider may not appear in the KeyStore Type parameter drop-down list. If the Security Provider that you want to use not appear in the list, use the "Add New Security Provider" link to add the Security Provider.
*To add a security provider
1. Open Integration Server Administrator if it is not already open.
2. In the Security menu of the Navigation panel, click Keystore.
3. Click Add Security Provider.
4. In the Add Security Provider area of the screen, in the Security Provider Class field, enter the Java class name of the security provider to be used for additional keystore and truststore file types. For example, the name of nCipher's security provider is com.ncipher.provider.km.nCipherKM.
Note:
Ensure that the corresponding jar file is in the classpath.
If the keystore type supported by the HSM is not one of the defaults supported by Integration Server, modify the property watt.security.keyStore.supportedTypes or watt.security.trustStore.supportedTypes respectively to add a new keystore type for the keystore or truststore.
5. Click Add Provider.
Integration Server adds the security provider to the list of available security providers. If the keystore type supported by the newly added security provider is one of the default keystore types (JKS, PKCS12) supported by Integration Server and you select that keystore type in the Keystore Type list for an HTTPS or FTPS port, the corresponding provider will be available in the Provider list for that keystore type.
If the keystore type is not supported, modify the properties watt.security.keyStore.supportedTypes and watt.security.trustStore.supportedTypes to add a new keystore type for the keystore and truststore.