It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×10,914
×1,192

question asked: May 08 '14, 6:48 p.m.
question was seen: 4,888 times
last updated: May 20 '14, 12:18 a.m.

Related questions

Java API SSL client fails to connect to Build Forge

0
Peter Moraza (48●19●24) | asked May 08 '14, 6:48 p.m.
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

Comments
Peter Moraza commented May 20 '14, 12:18 a.m.

Hi Eric,


My Java test client is based on one of the BF client examples but instead exercises the SecureAPIClientConnection class as yours does, and it is very similar to the file in your Work Item 24712, except it simply displays the BF projects. Thanks for sharing, it helped me confirm that my code should work. I suspect my issue might be with the keystore and truststore files supplied to me. The .p12s refer to a hostname that does not match the hostname of the actual Build Forge server. I'll need to confirm how the keys were generated and the environment setup. Thanks for sharing!

Peter

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Donald Nong (14.5k●6●14) | answered May 09 '14, 1:36 a.m.
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.
Comments
Peter Moraza commented May 09 '14, 7:38 p.m.
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)

Donald Nong commented May 11 '14, 8:29 p.m.

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.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.