IBM MQ Native step failing with 2400 -MQ 2400: MQRC_UNSUPPORTED_CIPHER_SUITE
search cancel

IBM MQ Native step failing with 2400 -MQ 2400: MQRC_UNSUPPORTED_CIPHER_SUITE

book

Article ID: 139743

calendar_today

Updated On:

Products

Service Virtualization

Issue/Introduction

When using the IBM MQ native step, the following unsupported cipher suite error comes up: 
2400 -MQ 2400: MQRC_UNSUPPORTED_CIPHER_SUITE

Cipher Suite used: SSL_RSA_WITH_AES_256_CBC_SHA256
MQ version: 8.0.0.4
MQ client jars used: com.ibm.mq.allclient.jar, com.ibm.mq.commonservices.jar
DevTest version: 10.x

Environment

All supported DevTest releases.

Resolution

The following document was used:

IBM MQ and SSL/TLS

 
Specific steps from that document that resolved the issue:

1 (step 4.6.1 and step 4.6.2) Copy the 'IBM JSSE jars' to JRE_HOME/lib/ext used by DevTest (i.e. jre\lib\ext).

2 (step 4.6) Add in local.properties:
com.ibm.mq.cfg.useIBMCipherMappings=False

3a (step 4.6.2) In the java.security (jre\lib\security) file, add com.ibm entries 12-16 so it now looks like:

security.provider.1=sun.security.provider.Sun
security.provider.2=sun.security.rsa.SunRsaSign
security.provider.3=sun.security.ec.SunEC
security.provider.4=com.sun.net.ssl.internal.ssl.Provider
security.provider.5=com.sun.crypto.provider.SunJCE
security.provider.6=sun.security.jgss.SunProvider
security.provider.7=com.sun.security.sasl.Provider
security.provider.8=org.jcp.xml.dsig.internal.dom.XMLDSigRI
security.provider.9=sun.security.smartcardio.SunPCSC
security.provider.10=sun.security.mscapi.SunMSCAPI
security.provider.11=apple.security.AppleProvider
security.provider.12=com.ibm.jsse2.IBMJSSEProvider2
security.provider.13=com.ibm.crypto.provider.IBMJCE
security.provider.14=com.ibm.security.jgss.IBMJGSSProvider
security.provider.15=com.ibm.security.cert.IBMCertPath
security.provider.16=com.ibm.security.sasl.IBMSASL

3b (step 4.5) In java.security comment out this line:
# jdk.tls.disabledAlgorithms=SSLv3, RC4, DH keySize < 768

4.  (Step4.6.3) Configure a SSL Context asset with that JCE provider.

Additional Information

Found that in some cases only step 1 and 2 are needed.