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 Future consideration
Workspace MQ, MQ Advanced & MQ Appliance
Created by Guest
Created on Jun 22, 2022

RELATED IDEAS

.Net Standard version(9.x) of IBM MQ library should honor WMQ_SSL_CIPHER_SPEC Config on MQ connection factory while doing TLS Handshake with MQ Server.

As of now, 9.2 version of .netstandard lib of IBM MQ uses OS cipher suite to define the client cipher during TLS handshake with server and only uses WMQ_SSL_CIPHER_SPEC to determine the TLS protocol of cipher which is misleading.

Because of current behavior of lib, during SSL handshake it always pick the highest order cipher(in MQ server) for TLS handshake and try to match it with channel cipher. For example if I am using 9.1 on MQ Server, TLS handshake will always happen with TLS_RSA_WITH_AES_128_CBC_SHA256 while if I am using 9.2 cipher TLS handshake will always happen with TLS_RSA_WITH_AES_256_GCM_SHA384.

Please refer documentation for the default order of cipher - https://www.ibm.com/docs/en/ibm-mq/9.2?topic=cipherspecs-cipherspec-order-in-tls-handshake.

Even if we change the order of cipher in mq.ini, We will always pick the first cipher in the list. This create a problem in following use case.

I have two app running on same machine (Windows/Linux) and each trying to connect to channel which have different cipher from each other.

Idea priority Urgent
  • Admin
    Mark Taylor
    Reply
    |     Sep 6, 2022

    Something we would like to do, but it does first require an update to the MQ package to be based on .Net 6 frameworks. It can't be added to the current implementation.

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.