Skip to main content
Summary Getting a "No available certificate or key corresponds to the SSL cipher suites" error in Artix 5.5 JAX-WS client
Article Number 16797
Environment All Supported Operating Systems Artix 5.5 Artix JAX-WS Runtime
Question/Problem Description Getting a "No available certificate or key corresponds to the SSL cipher suites" error in Artix 5.5 JAX-WS client

Getting the following error:

    javax.net.ssl.SSLException: No available certificate or key corresponds to the SSL cipher suites which are enabled.
        at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.checkEnabledSuites(SSLServerSocketImpl.java:303)
        at com.sun.net.ssl.internal.ssl.SSLServerSocketImpl.accept(SSLServerSocketImpl.java:253)
        at org.mortbay.jetty.security.SslSocketConnector.accept(SslSocketConnector.java:172)
        at org.mortbay.jetty.AbstractConnector$Acceptor.run(AbstractConnector.java:707)
        at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:497)

 When configuring Jetty SSL connector in Artix 5.5 JAX-WS
Clarifying Information
Error Message
Defect/Enhancement Number
Cause Missing .p12 file "password" property
Resolution

When configuring the Jetty SSL connector in Artix JAX-WS, two types of keystore are supported: JAVA Keystore format ".jks" and PKCS12 keystore format ".p12".

If  PKCS12 keystore is used, it requires two passwords: 1)"password" is the password for the keystore file, and 1)"keyPassword" is the password for the individual key itself. If the PKCS12 store is also used as a trust store (contains a CA), a third password properly 3)"trustPassword" is needed.
Workaround
Notes
Attachment
Created date: 06 September 2011
Last Modified: 13 February 2013
Last Published: 23 June 2012
First Published date: 10 September 2011

#Orbix
#KnowledgeDocs
Terms & ConditionsAccessibility statement