I'm trying to create a SSL connection between Tibco and a specific queue channel. I've created a self signed certificate and provided the client wit the key and configured the channel with SSLCIPH.

But the connection does not work and we get the following error
AMQ9639E: Remote channel 'UAT.SVRCONN.XXX.01' did not specify a CipherSpec.

but this is done by following cmd
ALTER CHANNEL(UAT.SVRCONN.XXX.01) CHLTYPE(SVRCONN) TRPTYPE(TCP) SSLCIPH(TLS_RSA_WITH_AES_128_CBC_SHA256) MCAUSER('XXX') SSLCAUTH(REQUIRED)


------------------------------
Ilhan Yavuz
------------------------------

I suspect that you observed the AMQ9639E message in the queue manager AMQERR01.LOG file? If so, then when it says "Remote channel did not specify a CipherSpec" it is referring to the client end of the channel. Can you provide us with details on how you set the CipherSpec in the client configuration? Are you, for example, using a CCDT?

Cheers,
Morag

------------------------------
Morag Hughson
MQ Technical Education Specialist
MQGem Software Limited
------------------------------

Have you tried specifying the certificate label on the channel? Did it make a difference?

------------------------------
FJ Brandelik

------------------------------

Hi Ilhan,

You have shown us the definition of the server side of the connection. This is the SVRCONN channel definition. The client side (represented commonly by a CLNTCONN channel definition in the channel table file) also needs to specify the TLS cipher.

The Tibco environment then needs to be configured to have a key store, and to use the channel table to pick up the correct channel values, or you need to configure that through code in the Tibco environment, or perhaps through a JNDI definition of the connection factory.

Regards,




------------------------------
Neil Casey
Senior Consultant
Syntegrity Solutions
Melbourne
IBM Champion (Cloud) 2019
+61 (414) 615-334
------------------------------