You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using MQ client 9.3 the SNI route is only needed if using per channel certs. The SNI route is pretty ugly, requiring channel names to be unique across the whole cluster, so it would be nice to relax that requirement. I found the first sample works if I remove the SNI route, add the following client.ini file:
SSL:
OutboundSNI=HOSTNAME
And set the following env var:
export MQCLNTCF=`pwd`/client.ini
The text was updated successfully, but these errors were encountered:
When using MQ client 9.3 the SNI route is only needed if using per channel certs. The SNI route is pretty ugly, requiring channel names to be unique across the whole cluster, so it would be nice to relax that requirement. I found the first sample works if I remove the SNI route, add the following client.ini file:
SSL: OutboundSNI=HOSTNAME
And set the following env var:
The text was updated successfully, but these errors were encountered: