Configuring an HTTPS or FTPS Port

If you want to allow only secure connections to the server, ensure that the primary port uses an HTTPS or FTPS port and delete all other non-HTTPS or non-FTPS ports. Add as many additional HTTPS or FTPS ports as you want. Make sure no other applications are listening on the port you want to use.

You can further configure HTTPS and HTTPS diagnostic ports and the pub.client:http service, or FTPS ports and the pub.client:ftp service to use Java Secure Socket Extension (JSSE) for handling inbound and outbound communications. JSSE is required to support TLS 1.1 or 1.2. When configured, Integration Server uses the JSSE socket factory to create outbound socket connections. For more information about configuring ports to use JSSE, see Configuring Ports. For more information about setting JSSE in the pub.client:http service and pub.client:ftp service, see webMethods Integration Server Built-In Services Reference.

Note:

When you configure a port to use JSSE and a client presents a certificate that Integration Server does not trust, Integration Server rejects the request and it will not fall back to use basic credentials (user name/password). If there is no certificate mapping, Integration Server issues an invalid credentials error.