IBM Support

Sterling B2B Integrator's REST API UI (i.e., B2BAPIs/svc) is not accessible over https due to javax.net.ssl.SSLHandshakeException: no cipher suites in common

Troubleshooting


Problem

Sterling B2B Integrator's REST API UI (i.e., B2BAPIs/svc) is not accessible over https URL

Symptom

None of the applications hosted on Sterling B2B Integrator's Liberty server are accessible over https; http URLs work well.
Following are the example URLs fail to load and present "Secure Connection Failed" error on browser
https://<host>:<LIBERTY_HTTPS_PORT>/B2BAPIs/svc
https://<host>:<LIBERTY_HTTPS_PORT>/propertyUI
liberty/wlp/usr/servers/SIServer/logs/messages.log shows exception as below.
[10/25/21 14:53:20:477 EDT] 00000045 com.ibm.ws.channel.ssl.internal.SSLHandshakeErrorTracker     E CWWKO0801E: Unable to initialize SSL connection. Unauthorized access was denied or security settings have expired. Exception is javax.net.ssl.SSLHandshakeException: no cipher suites in common
        at com.ibm.jsse2.D.A(D.java:655)
        at com.ibm.jsse2.as.b(as.java:427)
        at com.ibm.jsse2.as.c(as.java:376)
        at com.ibm.jsse2.as.wrap(as.java:479)
        at javax.net.ssl.SSLEngine.wrap(SSLEngine.java:45)
        at com.ibm.ws.channel.ssl.internal.SSLUtils.handleHandshake(SSLUtils.java:695)
        at com.ibm.ws.channel.ssl.internal.SSLConnectionLink.readyInbound(SSLConnectionLink.java:589)
        at com.ibm.ws.channel.ssl.internal.SSLConnectionLink.ready(SSLConnectionLink.java:336)
        at com.ibm.ws.tcpchannel.internal.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:167)
        at com.ibm.ws.tcpchannel.internal.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:75)
        at com.ibm.ws.tcpchannel.internal.WorkQueueManager.requestComplete(WorkQueueManager.java:504)
        at com.ibm.ws.tcpchannel.internal.WorkQueueManager.attemptIO(WorkQueueManager.java:574)
        at com.ibm.ws.tcpchannel.internal.WorkQueueManager.workerRun(WorkQueueManager.java:958)
        at com.ibm.ws.tcpchannel.internal.WorkQueueManager$Worker.run(WorkQueueManager.java:1047)
        at com.ibm.ws.threading.internal.ExecutorServiceImpl$RunnableWrapper.run(ExecutorServiceImpl.java:239)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
        at java.lang.Thread.run(Thread.java:822)
Caused by: javax.net.ssl.SSLHandshakeException: no cipher suites in common
        at com.ibm.jsse2.k.a(k.java:43)
        at com.ibm.jsse2.as.a(as.java:105)
        at com.ibm.jsse2.D.a(D.java:397)
        at com.ibm.jsse2.D.a(D.java:654)
        at com.ibm.jsse2.F.b(F.java:534)
        at com.ibm.jsse2.F.a(F.java:817)
        at com.ibm.jsse2.F.a(F.java:492)
        at com.ibm.jsse2.D.s(D.java:286)
        at com.ibm.jsse2.D$b.a(D$b.java:3)
        at com.ibm.jsse2.D$b.run(D$b.java:2)
        at java.security.AccessController.doPrivileged(AccessController.java:770)
        at com.ibm.jsse2.D$c.run(D$c.java:14)
        at com.ibm.ws.channel.ssl.internal.SSLUtils.handleHandshake(SSLUtils.java:751)

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"ARM Category":[{"code":"a8m0z000000brQLAAY","label":"REST API-\u003ELiberty Server"}],"ARM Case Number":"TS006703408","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0.3;6.1.0"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
26 October 2021

UID

ibm16508603

Page Feedback