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 Not under consideration
Workspace App Connect
Created by Guest
Created on Jan 19, 2017

Add keyalias property CICSRequest node

IIB Restriction/Limitation:
The IIB v10 CICSRequest node does not have a keyalias property.

Idea priority Medium
RFE ID 99909
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Mar 12, 2023

    Idea Review. As part of our policy for regularly reassessing aged ideas we have recently discussed this enhancement request again. Unfortunately, with a single vote since its creation in 2017, we do not intend to take this idea further forward. We do note that both the IIBv10 configurable service, and the ACEv11/v12 policy enable you to direct the CICSRequest node to a specific keystore, which means that you could use separate keystores (with separate certificates) for the sake of different CICS systems. We realise that this is not quite what was asked for (a single keystore for all purposes with the use of a keyalias to identify which cert should be used for which node) but a decent workaround nevertheless. In case the workaround sounds helpful to future readers, we include information links to the v10 and v11 documentation on this topic:

  • Guest
    Oct 16, 2020

    RFE Review. Thank you for raising this RFE and apologies for the length of time it has been in Submitted status. We agree that this suggested enhancement would improve the product. Staus of the RFE is updated to Uncommitted Candidate.