IBM Rational Quality Manager (RQM) copy utility raises SSL_TLS SSLContext and certificates exceptions whether source and target projects are on the same server or different servers. A workaround is available to resolve this issue.
Here is an example from the command line: Error:
Command used: java -jar RQMCopyUtility.jar -s=https://rqmServer1:9443/jaz z/secure/service/com.ibm.rqm.integration.service.
IIntegrationService/resources/<Source_project> -us=**** -pws=**** -
d=https://rqmServer2:9443/jazz/secure/service/com.ibm.rqm.integration.service. IIntgrationService/resources/<Target_project> -a=template -l=copyUtilitylog.txt
Here is the subsequent error:
java.security.NoSuchAlgorithmException: SSL_TLS SSLContext not available
Unable to create SSL_TLS context, trying SSLv3
SEVERE: Error logging in to source: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Certificates does not conform to algorithm constraints
JDK7 has changed the default Java security settings to disable MD2 algorithm to sign SSL certificates.
Resolving The Problem
The default Java security settings can be re-enabled by editing JDK_HOME/jre/lib/security/java.security and commenting out the following line:
Windows path to the config file: <Java install path>\Java\jre7\lib\security
You can also revert to an older version of the Java version to resolve this issue.
16 June 2018