Problems working with a secured server using SSL connections
How to work around the SSLSocketFactory and SSLHandshakeException error messages when you are trying to communicate to a secured server by using a Secure Sockets Layer (SSL) connection within the workbench.
Important: Applicable to WebSphere® Application Server traditional
java.net.SocketException: java.lang.ClassNotFoundException: Cannot find the specified class com.ibm.websphere.ssl.protocol.SSLSocketFactoryHere is a list of known tools where this SSLSocketFactory error message is displayed:
- Web services wizard retrieving an HTTPS WSDL
- Web Services Explorer running against a secured WebSphere Application Server
- Deploying web services to the Axis runtime environment
- Installing Rational® Asset Manager with an SSL enabled WebSphere Application Server
SSLSocketFactory
error message, is to look for the
following line in the com.ibm.ws.ast.st.core.prefs file available in the
x:\workspace\.metadata\.plugins\org.eclipse.core.runtime\.settings,
where x:\workspace is the directory of your
workspace.isUseIBMSSLSocketFactory=true
Replace true
with false. Then, restart the workbench.After you change the
isUseIBMSSLSocketFactory property to false, you might
encounter the following SSLHandshakeException error
message:
Server.userException javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.g: No trusted certificate foundTo resolve the SSLHandshakeException error message when the isUseIBMSSLSocketFactory property is set to false, see the Configuring the IBM® JRE to talk to a secured WebSphere Application Server topic for instructions for running the iKeyman tool to work around this problem.
Modifying the isUseIBMSSLSocketFactory property to
false might cause the SSLHandshakeException error
message to persists when you are connecting or switching for the first time to a secured WebSphere Application Server by using an SSL connection
within the
workbench:
Server.userException javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.g: No trusted certificate foundThe workaround for this SSLHandshakeException error message, is to change back the isUseIBMSSLSocketFactory property to true. Look for the following line in the com.ibm.ws.ast.st.core.prefs file available in the x:\workspace\.metadata\.plugins\org.eclipse.core.runtime\.settings, where x:\workspace is the directory of your workspace.
isUseIBMSSLSocketFactory=false
Replace
false with true. Then, restart the
workbench.