Hello Santosh,
Mr. Google should have shown you the various MQ solutions that Capitalware offers.
Authentication: Since MQ v8, MQ provides a basic authentication mechanism. If you want a very robust solution for MQ authentication then have a look at
MQ Authenticate User Security Exit (MQAUSX). You can have 1 configuration per queue manager or 1 per channel or however you want it. It is supported on AIX, HP-UX, IBM i, Linux (x86, Power & zSystem), Solaris, Windows and z/OS.
Encryption: Capitalware offers 2 solutions:
MQ Channel Encryption (data infight) and
MQ Message Encryption (data at rest). One of the big differences between MQ Message Encryption (MQME) and MQ AMS is that MQME does NOT require certificates (neither does MQ Channel Encryption). And the headache of yearly renewal and deployment of certificates. Also, another big difference between MQ AMS and MQME is that MQME supports encryption/decryption of messages for BOTH queues and topics. MQME is supported on AIX, HP-UX, IBM i, Linux (x86, Power & zSystem), Solaris and Windows.
You can setup MQME to be in an MQ Security Grid (a term I coined), where MQME handles BOTH data inflight and data at rest.
You can review a presentation I gave at MQ Technical Conference in 2018 called
What's new in MQ Message Encryption.Regards,
Roger Lacroix
Capitalware Inc.