All,
I need everyone’s help in getting IBM to add a missing feature to AMQP & MQTT channels.
When IBM added direct support for MQTT to an MQ queue manager, I didn’t look very carefully at how IBM implemented the channel attributes (busy doing other things). Now IBM has added AMQP channel as of MQ v8.0.0.4 and a customer emailed me asking if MQAUSX would be supported for AMQP channels.
I looked in the MQ Knowledge Center at AMQP channel (which is a clone of MQTT):
http://www.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.ref.adm.doc/q123914_.htm?lang=en
And channel has the usual channels attributes like SSLPEER, SSLCIPH, MCAUSER, etc.. except there is no SCYEXIT (channel security exit) attribute.
All of the channels, Sender, Receiver, Server, Requester, Cluster-Sender, Cluster-Receiver, Server Connection and Client Connection, support channel security exit but not AMQP & MQTT channels.
The REALLY annoying part of IBM’s implementation is the CHLAUTH and CONNAUTH work with the new AMQP & MQTT channels as with all of the older channel types. You can read whatever you want into this decision but I think it is short-sighted. If you use your own security exit or BlockIP2 or one of mine (MQAUSX or MQSSX) then you are locked out.
Here is the RFE # 79245 I created:http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=79245
Please vote for it so that IBM will add channel security exit to AMQP & MQTT channels.
Regards,
Roger Lacroix
Capitalware Inc.
