Enable TLS1.2 for client side JDKs and Browsers

Review the following steps to enable TLS1.2 for client-side JDKs and browsers when working with Sterling B2B Integrator over HTTPS and or when running in NIST 800-131a strict mode.

To enable TLS1.2 for client JDKs and browsers:

Firefox Considerations

Firefox can only connect to one Sterling B2B Integrator server when using HTTPS, to resolve this issue:

The public certificate from the HTTPS server is stored in the cache. You can locate it in your Firefox browser from Options > View Certificates, where Sterling is the organization and ASI is the common name. This is the same syntax for all certificates using Sterling B2B Integrator HTTPS.

If this certificate is stored in the cache and you try to connect to another Sterling B2B Integrator instance, it will not work because the public certificate is a Sterling B2B Integrator instance and is different from the one in the cache. To work around this issue, select Confirm Security Exception and clear the box for Permanently store this exception. Doing this will allow certificate storage for only that specific session, allowing you to connect to another Sterling B2B Integrator instance when the browser is closed.