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.


Add a new idea Subscribe
Status Functionality already exists
Workspace MQ, MQ Advanced & MQ Appliance
Created by Guest
Created on Sep 18, 2024

RELATED IDEAS

Add support for Alias CipherSpecs in MQIPT

Hello,

since 9.2 IBM MQ support Alias CipherSpecs/CipherSuites, that is a keyword such as ANY_TLS13_OR_HIGHER for which the queue manager and the client will negotiate the best available CipherSpec/CipherSuite. This saves effort in constantly updating cipher suites. However, this does not work with IBM MQIPT. As per https://www.ibm.com/docs/en/ibm-mq/9.3?topic=thru-ssltls-support-in-mqipt, these CipherSuites aren’t supported. Please add this feature to MQIPT, too.

Thank you.

 

Idea priority High
  • Admin
    Mark Taylor
    Reply
    |     Oct 8, 2024

    From Development:


    This function is already possible in MQIPT, but in a different way than by specifying the alias CipherSpecs that MQ provides.

    In an MQIPT route, the the CipherSuite and the protocol are specified by using two separate properties. For example, SSLClientCipherSuites and SSLClientProtocols. Specifying only the protocol, and not the CipherSuite, allows Java to negotiate the strongest CipherSuite that is also supported by the other endpoint. To connect to a channel that is using the ANY_TLS13 Cipher Suite, for example, the MQIPT route could be defined with SSLClientProtocols=TLSv1.3, and SSLClientCipherSuites left blank.

    This is essentially the same behaviour as the MQ alias Cipher Specs. The only aspect that is missing from MQIPT is the "OR_HIGHER" part of the alias Cipher Specs. However, a very close result can be achieved in MQIPT by specifying more than one protocol in the route definition.


By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.