What is the blocker for TLS 1.2 for Mac OS RTC Client
![]()
Hi,
Under a corporate mandate to enable TLSv1.2 on our CLM applications. In https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.jazz.install.doc/topics/t_enable_tls1.2_rtc.html&scope=null one finds: Limitations
The following portions of the CLM product stack do not yet support TLS 1.2.
|
Accepted answer
![]() I think I have found the solution and there is no need to raise an enhancement request - the RTC 6.0.3 Client for Eclipse 4.2.x IDE works perfectly with TLSv1.2, and it even comes bundled with a JDK 1.7 (Oracle Java SE 1.7.0_101).
-Dosgi.requiredJavaVersion=1.7 You will then get the below error message when launching RTC. Note that 1.6.0_65 is the Apple Java version, and all other installed JVMs (OpenJDK and Oracle Java) are ignored. Version 1.6.0_65 of the JVM is not suitable for this product. So, if you can use RTC 6.0.3 Client for Eclipse 4.2.x IDE, use it. Otherwise, use an Eclipse 4.2 base and install RTC on top of it - verify that the Eclipse base can be launched with Java 7 or 8 first. Kevin Ramer selected this answer as the correct answer
Comments Thank you, Donald. I presumed that the version of Java in use had more to do with making a TLS v1.2 connection than the RTC client features. I passed this info along to a MacOS user, but with the suggestion to maybe try Eclipse Luna + RTC 6.0.2 P2 ( I use that combination daily on my RHEL 6.8 platform ). We're on 6.0.2 so even though 6.0.3 would do the TLS....
That's right. If you look at the stack trace in the other answer that I posted, you will see that the "TLSv1.2 SSLContext not available" error is thrown by Java itself. That actually prompted me to do further research and find out the information that I posted in this answer.
|
One other answer
![]() You should raise an enhancement request to the RTC development, I believe. If I enable debugging, here is what I see in the .log file.
|
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.
Comments
So, no one knows ?
Maybe you need to raise a request for enhancement to get TLS working with eclipse on MAC OS.
With Rational or Eclipse Development ?
No one ever said where the enhancement should be opened...
FWIW: I unzipped a 6.0.2 macos 64 bit and I can use the scm utility to successfully connect to a TLSv1.2 enabled server and do query ( e.g. list workspaces ) w/o issue.
However, users of our applications with MacOS cannot use Eclipse IDE. I can't verify on mac as I can't successfully connect to the "display"