Connections 6.0 additional setting when forcing TLS v1.2
Preventive Service Planning
Abstract
IBM Connections 6.0 with Java 8 requires an additional setting when forcing TLS v1.2
Content
IBM Connections 6.0 with Java 8 requires an additional setting when forcing TLS v1.2 to prevent errors from servers that accept only TLS v1.2. Follow the instructions in the help topic Forcing traffic to use TLS 1.2 then enable the JVM argument "-Dcom.ibm.jsse2.overrideDefaultTLS=true" on the AppServer so that Java 8 returns TLS 1.0, TLS 1.1 and TLS 1.2 protocols for SSLContext. The Client will pick highest Protocol TLS 1.2 in TLS Handshake when it sends ClientHello to Server for establishing TLS 1.2 connections.
Note: This setting is not for previous releases that use Java 6
Instructions for setting the JVM argument:
- Open the Websphere Integrated Solution Console
- Select Server Types -> Websphere Application Server
- For each Application Server expand Java and Process Management then go to Process definition->Java Virtual Machine
- Add the following in Generic JVM arguments: -Dcom.ibm.jsse2.overrideDefaultTLS=true
- Click OK and Save Changes
- Restart the Application Server to apply the changes
Document information
More support for:
IBM Connections
Content Manager
Software version: 6.0
Operating system(s): AIX, Linux, Windows
Reference #: 2007135
Modified date: 22 August 2017