Skip to Main Content
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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.


Status Delivered
Created by Guest
Created on Feb 2, 2019
Merged idea
This idea has been merged into another idea. To comment or vote on this idea, please visit MESNS-I-617 In transit MQ encryption without SSL certificates.

Server-side enablement of MQ Channel encryption Merged

enable server-side encryption of MQ Channels using MQ Server certificate.
currently to enable encryption on an MQ Channel you need to have a certificate store on the client side and tell the client to use which encryption. A lot of commercial packages and cloud solutions have implemented only a sub-set of MQ options on the API and often do not allow for local storage (specially in Cloud) of files that contain certificates (kdb for C or jks for java clients)
The behaviour of the client has to be changed so the MQ server can pass it's certificate (public part) in the handshake and enforce encryption on the communication between client and server.

Idea priority Medium
RFE ID 129623
RFE URL
RFE Product IBM MQ
  • Guest
    Reply
    |
    Jun 28, 2024
    V9.4 includes a TLS mode that means clients do not need CA certs
  • Guest
    Reply
    |
    Sep 22, 2020

    We are considering a way to meet this requirement as part of a future update to MQ.

  • Guest
    Reply
    |
    Feb 8, 2019

    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.

  • Guest
    Reply
    |
    Feb 5, 2019

    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.