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
Created by Guest
Created on Sep 4, 2026

Multiple kdb file support in IBM App Connect Enterprise

Currently, an ACE Integration Runtime is constrained to a single global CMS Key Repository (.kdb / .sth) for IBM MQ client TLS connections (configured via mqKeyRepository in server.conf.yaml, node.conf.yaml, or MQCLNTCF/mqclient.ini).

 

While a single KDB file can technically store multiple certificates, this single-repository constraint creates major operational, governance, and security challenges in enterprise environments where multiple message flows connect to disparate Queue Managers owned by different teams, lines of business (LOBs), or external third parties with uncoordinated certificate lifecycles.

 

We request that IBM ACE support multiple independent CMS Key Repositories (.kdb) per Integration Runtime, configurable on a per-connection basis (e.g., via MQEndpoint policies or MQ node properties), alongside support in the App Connect Operator to mount multiple keystore configurations cleanly.

Idea priority High