Integration
This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
We are considering a way to meet this requirement as part of a future update to MQ.
MQ already supports a being able to configure a channel so the client side of a TLS connection does not require a private cert. I am using the word client in the TLS sense, meaning what is initiating the network connection. In MQ examples of a TLS client include the "MQ client end" of a SVRCONN, SDR, CLUSSDR, SVR when it is initiating the connection to a RCVR or RQSTR, and a RQSTR when it is initiating a connection to a SVR or SDR channel.
To tell the queue manager that you do not require the client to have a cert you need to specify a SSLCIPH value in addition to SSLCAUTH(OPTIONAL) and a blank SSLPEER.
On the client side you still need to have the root certs to allow the client to trust the queue manager's cert, and this is the same as how a browser behaves, it still needs a "trust store".
In this setup you still need something to perform authentication of the client, for example with a SVRCONN this could be CONNAUTH.
I agree to have a simple solution to add encryption to aclient channel without the need to the applicaton to deal with certificates, which may be painful, depending on the certificate management tools. If you need only encryption on the wire without authentification of the client, this is very helpful.