It's all about the answers!

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

×42,877
×6,036

question asked: Oct 30 '17, 7:20 p.m.
question was seen: 2,119 times
last updated: Oct 31 '17, 5:17 p.m.

Related questions

Why will Urban Code Release API not work in RTC follow-up participant?

0
Robert Huet (231●1●39●84) | asked Oct 30 '17, 7:20 p.m.

 I've written some Java code that uses the Urban Code Release Java Client Library.  This runs fine in a stand-alone Java app, but logging into URelease fails when running from an RTC follow-up participant plug-in.


The following error appears in the RTC client:

I'm running RTC 6.0.2 with Websphere Liberty, and have configured for TLS 1.2.  Any ideas?

The following error appears in the ccm.log file:
java.lang.IllegalArgumentException: Only TLS1.2 protocol can be enabled in SP800_131 strict mode
at com.ibm.jsse2.pb.a(pb.java:151)
at com.ibm.jsse2.pb.b(pb.java:14)
at com.ibm.jsse2.pb.<init>(pb.java:115)
at com.ibm.jsse2.qc.a(qc.java:261)
at com.ibm.jsse2.qc.<init>(qc.java:864)
at com.ibm.jsse2.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:14)

The URelease api call that fails is:
loginAs("https://release.cs.server.com/", "userid", "pswd");

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Robert Huet (231●1●39●84) | answered Oct 31 '17, 5:17 p.m.

 It turns out that the UrbanCode Release server was not set to use TLS 1.2, but the CLM instance was.  So the system was trying to use TLS1.2 on a server that did not support it.

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.