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:
- Verify that you are using JDK 1.7. TLS1.2 is only supported on JDK 1.7. For additional information, see:http://docs.oracle.com/javase/7/docs/technotes/guides/security/SunProviders.html
- From your Windows Control Panel, in the search box, typejavato locate and open the Java Control Panel.
- On the Java Control Panel window, click theAdvancedtab.
- Select TLS1.2 in Advanced Security Settings and clickOK.
To enable TLS1.2 for Internet Explorer, version 8:
- On the Internet Explorer browser window, from the Tools menu, selectInternet Options.
- Click theAdvancedtab.
- SelectTLS1.2in the Advanced Security Settings.
Firefox Considerations
Firefox can only connect to oneSterling B2B Integratorserver when using HTTPS, to resolve this issue:
- When Firefox connects to a website using HTTPS when the certificate of the server is self-signed, a dialog box appears. SelectAdd Exceptionto continue.
- A new dialog appears asking you to confirm. ClickConfirm Security Exceptionto launch the HTTPS connection.
The public certificate from the HTTPS server is stored in the cache. You can locate it in your Firefox browser fromOptions > View Certificates, where Sterlingis the organization and ASIis the common name. This is the same syntax for all certificates using Sterling B2B IntegratorHTTPS.
If this certificate is stored in the cache and you try to connect to anotherSterling B2B Integratorinstance, it will not work because the public certificate is a Sterling B2B Integratorinstance and is different from the one in the cache. To work around this issue, select Confirm Security Exceptionand 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 Integratorinstance when the browser is closed.
