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 Not under consideration
Created by Guest
Created on Jul 19, 2024

Provide aliases of SSL related attributes in runmqsc

Existing runmqsc commands for channels with TLS parameters (SSLCIPH, SSLPEER etc) lead to cognative dissonance as they no longer control SSL, but rather TLS. The documentation and GUI (MQ Explorer and MQ Console) have updated the names of these fields, but runmqsc is unchanged since SSL was introduced in MQ 5.3 or so.

Although the existing attribute names need to continue to be supported to allow existing scripts to work, they should have new TLS based aliases, such as TLSCIPH and TLSPEER which would fully interoperate with the legacy attribute names.

It can be more difficult than it should be to persuade security reviewers that configurations are correctly supporting only trusted ciphers when they audit the configuration and find that attributes like SSLCIPH are used to set the values in MQ.iiii

Idea priority Low
  • Admin
    Mark Taylor
    Reply
    |
    Jul 30, 2024

    Even though it would be possible to provide alias for input options, there would not be a good solution for deciding what to use in output. "SSL" is here to stay - not just in MQ, but other products are also introducing options with SSL in the name. For example, Spring's SSLBundles which is only a year old.