It's all about the answers!

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

×10,944
×6,103

question asked: Feb 20 '20, 9:10 p.m.
question was seen: 907 times
last updated: Feb 20 '20, 11:14 p.m.

Related questions

RQM Copy Utility Chokes on TLS 1.2

0
Andy Lapping (68●3●9) | asked Feb 20 '20, 9:10 p.m.

 Trying to use the RQM copy utility to copy items from one server to another. The source server uses TLS1.2 - the copy utility chokes on that:


 02:02:16,543+0000 [main]  INFO com.ibm.rqm.ct.CopyUtil: Attempting to create SSL_TLS context
21 Feb 2020 02:02:16,637+0000 [main] ERROR com.ibm.rqm.ct.CopyUtil: SSL_TLS SSLContext not available
21 Feb 2020 02:02:16,637+0000 [main]  INFO com.ibm.rqm.ct.CopyUtil: Unable to create SSL_TLS context, trying SSLv3
21 Feb 2020 02:02:18,355+0000 [main] ERROR com.ibm.rqm.ct.CopyUtil: Error logging in to source: javax.net.ssl.SSLException: Received fatal alert: protocol_version
javax.net.ssl.SSLException: Received fatal alert: protocol_version
at sun.

Is there any way to force it to use TLS 1.2 ? 

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Andy Lapping (68●3●9) | answered Feb 20 '20, 11:11 p.m.
edited Feb 20 '20, 11:14 p.m.

Thanks to Brian Lahaie for this one - a command line switch worked - well at least it got past the TLS error anyways:


java -Dcom.ibm.team.repository.transport.client.protocol="TLSv1.2" -jar RQMCopyUtility.jar -s=xxxxxxxxx


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.