Compliance Event Manager SSL/TLS Setup Java error HANDSHAKE_FAILURE no cipher suites in common
search cancel

Compliance Event Manager SSL/TLS Setup Java error HANDSHAKE_FAILURE no cipher suites in common

book

Article ID: 265393

calendar_today

Updated On:

Products

Compliance Event Manager

Issue/Introduction

After setting up SSL/TLS between the browser and Tomcat server for Compliance Event Manager, the following error is seen in the browser:

tomcatserver.url uses an unsupported protocol.

ERR_SSL_VERSION_OR_CIPHER_MISMATCH

With debug turned on for Tomcat, the following error can be seen:

javax.net.ssl|SEVERE|1C|https-jsse-nio-xxxx-exec-1|date time Thread.java:1178|Fatal (HANDSHAKE_FAILURE): no cipher suites in common (                                                          

"throwable" : {                                                               
  javax.net.ssl.SSLHandshakeException: no cipher suites in common

The Compliance Event Manager documentation for this process was followed. What is causing this error?     

Environment

Release : 6.0

Resolution

The Tomcat Server certificate's private key was stored in ICSF. When this is the case, the keystoreType parameter in the Tomcat server.xml file needs to be changed from JCERACFKS to JCECCARACFKS

<!-- Define a SSL HTTP/1.1 Connector on port 8443 -->
     <Connector port="30308" maxHttpHeaderSize="8192"
           maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
           enableLookups="false" disableUploadTimeout="true"
           SSLEnabled="true"
           algorithm="IbmX509"
          acceptCount="100" scheme="https" secure="true"
          clientAuth="false" sslProtocol="TLS" 
          sslEnabledProtocols="TLSv1.2,TLSv1.1,TLSv1"
          keystoreType="JCECCARACFKS"
          keystoreFile="safkeyring://KEY_RING_OWNER/KEY_RING_NAME"
       sslImplementationName="com.ca.sslsocket.CASSLImplementation" />

Update the keystoreType parameter, then recycle the Tomcat started task.