Securing 1SMS with HTTPS

1SMS can be configured to communicate over HTTPS with self-signed certificates.

WebLogic

Note: For full details on how to set up HTTPS in your WebLogic environment, please see the Oracle product documentation.

Extra Configuration

Once HTTPS has been set up in your WebLogic environment, a few extra configuration steps are required.

1Exchange

Due to limitations with third party libraries, 1Exchange must be able to communicate internally using the non-SSL endpoint.

Ensure the restBaseUrl parameter is configured to refer to the non-SSL endpoint, even when not in a load balanced environment.

  1. Set the restBaseUrl parameter for the MSExchange server to refer to the unsecured listen port.

  2. Restart the Exchange server.

SOA Domain

An extra step is required to get 1Workflow calling services over HTTPS when using custom certificates or all calls will fail.

Update the -Djavax.net.ssl.trustStore parameter to point to your custom trust store.

Note: Ensure that If using secured authentication providers (see Authentication Provider Setup), the certificate(s) for them are added to your custom trust store

  1. As per the Oracle product documentation, update the -Djavax.net.ssl.trustStore parameter specified in the setDomainEnv file to point to your custom trust store.

    -Djavax.net.ssl.trustStore=C:\Security\trust.jks

  2. Restart the SOA server.

WildFly

For details on securing 1SMS with HTTPS in WildFly, please refer to 1SMS_Installation_Guide_Wildfly.pdf, as this is implemented during installation.