Integration
Hide about this portal


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 Submitted
Workspace MQ, MQ Advanced & MQ Appliance
Created by Guest
Created on Mar 19, 2025

RELATED IDEAS

MQ .NET Managed client - Use most secure common negotiated CipherSpec by default

See this idea on ideas.ibm.com

When I try to use the alias Ciphers (ANY_TLS12_OR_HIGHER) which are very popular now, it is silently ignored and instead it is defaulting to insecure TLS 1.0 by default. Can you change IBM MQ.NET managed client in this way :
- Use most secure CipherSpec when unknown (Alias or bad name) CipherSpec is specified instead of silently trying random TLS 1.0 CipherSpec. Do not try to use deprecated TLS 1.0 CipherSpecs.

- Check if TLS 1.0 is enabled or not in OS before trying to use it. In my case both client and MQ servers have TLS 1.0 server+client disabled server wide, but even so IBM MQ.NET managed client tries to use it so it fails. There is no good error logged when this happens also. Please log to event log.

- Log to event log error that your specified CipherSpec was not found and that it will try to negotiate other CipherSpec instead. Then we are aware of the issue and we can instead change to some CipherSpec that is accepted. It took days to find out and enable ANY cipher on new channel etc to see which was attempted.

Idea priority Medium

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.