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 Submitted
Workspace App Connect
Created by Guest
Created on Dec 13, 2025

Add option to select keyAlias for JmsInputNode/JmsOutputNode

Current Limitation:
In the existing implementation of JmsInputNode and JmsOutputNode, it is not possible to explicitly select a specific key alias for SSL/TLS connections. When a message flow requires different key aliases for a web service connection and a JMS connection, and both rely on the same keystore (e.g., jvmKeystore), the certificate selection process becomes non-deterministic. The system does not guarantee which certificate will be used, and relying on the order of entries in the keystore is not a viable solution.

Proposed Enhancement:
Introduce a new input property for JMS nodes that allows specifying the desired key alias. This feature would ensure deterministic certificate selection and resolve conflicts when multiple connections within the same flow require different key aliases.

Idea priority Urgent