Skip to Main Content

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Sep 25, 2023

MQ .NET Managed Client: Support alias CipherSpecs such as ANY_TLS13_OR_HIGHER

In MQ .NET Managed Client, please add support for alias CipherSpecs such as ANY_TLS13_OR_HIGHER. A queue manager provider supports several cipher specs and recommends we configure the alias CipherSpec rather than a specific cipher, however, MQ .NET Managed Client only works when configuring a single specific cipher.

Idea priority Medium
  • Admin
    Mark Taylor
    Nov 21, 2023

    The .Net client already uses the CipherSpec set at the application to determine only the version of TLS, rather than the specific cipher to be used. The global Group Policy setting at the OS level takes care of negotiating the actual CipherSpec. Making this more explicit, with the alias cipherspecs is something we hope to deliver in a future release.