Java API SSL client fails to connect to Build Forge
Hi,
We are trying to test connectivity to Build Forge 7.1.3.4 from a Java SSL client. I've followed the instructions in the following url to configure the Java client.
http://pic.dhe.ibm.com/infocenter/bldforge/v7r1m3/index.jsp?topic=%2Fcom.ibm.rational.buildforge.doc%2Ftopics%2Fconfig_sec_ssl_enabling_api_comm.html
The client terminates with RemoteServerAbortException.
com.buildforge.services.common.ssl.provider.JSSEProviderFactory initializeIBMCMSProvider
WARNING: {SSLProviderLoadFailed: [com.ibm.security.cmskeystore.CMSProvider]}
Exception in thread "main" com.buildforge.services.common.ssl.BuildForgeSSLEngine$RemoteServerAbortException: {SSLRemoteServerAbort}
at com.buildforge.services.common.ssl.BuildForgeSSLEngine.handshake(BuildForgeSSLEngine.java:257)
at com.buildforge.services.common.ssl.BuildForgeSSLEngine.init(BuildForgeSSLEngine.java:116)
at com.buildforge.services.client.api.SecureAPIClientBuffer.<init>(SecureAPIClientBuffer.java:25)
at com.buildforge.services.client.api.SecureAPIClientConnection.<init>(SecureAPIClientConnection.java:76)
at com.buildforge.services.client.api.SecureAPIClientConnection.<init>(SecureAPIClientConnection.java:72)
Unable to find any documentation for this error. Does anyone know what issue the BuildForgeSSLEngine.RemoteServerAbortException might indicate? TIA
Peter
One answer
Hi Peter,
The exception name itself may not say anything and the true cause is normally found at the bottom of the complete stack trace.
Based on the stack trace that you posted, I suspect that the client could not load the keystore and threw this exception.
The exception name itself may not say anything and the true cause is normally found at the bottom of the complete stack trace.
Based on the stack trace that you posted, I suspect that the client could not load the keystore and threw this exception.
Comments
Changed setup, increased trace. Now see details from .p12s. SSLProviderLoadFailed gone. Still see same RemoteServerAbortException. Any further ideas?
Build-Level: -20130318
adding as trusted cert:
Subject: CN=abc.mydomain.org
Issuer: CN=abc.mydomain.org
SSLContextImpl: Using X509ExtendedKeyManager
SSLContextImpl: Using X509TrustManager
Using SSLEngineImpl.
JsseJCE: Using SecureRandom IBMSecureRandom from provider IBMJCE
main, WRITE: TLSv1 Handshake, length = 141
Exception in thread "main" com.buildforge.services.common.ssl.BuildForgeSSLEngine$RemoteServerAbortException: {SSLRemoteServerAbort}
at com.buildforge.services.common.ssl.BuildForgeSSLEngine.handshake(BuildForgeSSLEngine.java:257)
Without the complete stack trace, I can't say much about it. Seeing that the exception occurred during handshake, I suspect that the problem was still with the certificate and/or algorithm.
Comments
eric yang
FORUM MODERATOR May 15 '14, 9:49 p.m.please see this use the SecureAPIClientConnection demo (24712)
https://jazz.net/jazz09/resource/itemName/com.ibm.team.workitem.WorkItem/24712
Peter Moraza
May 20 '14, 12:18 a.m.Hi Eric,