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 API Connect
Created by Guest
Created on Feb 16, 2018

Ability for an application (with associated ClientID/Secret) to be known across 2 API Connect Clouds

We currently have an external facing API Connect Cloud and an internal facing API Connect Cloud implementation. The former handles the security for the Channel APIs and the latter provides throttling and protection to the back-end system. For the case where we have an application requesting for access to a Channel API which is advertised through the external facing implementation and which results in API requests being routed through the internal API Connect implementtaion, we require the ability for the application details (incl. CliendID and Secret) to be known to each. Currently this requires one external facing API subscription and a secondary internal API subscription, with the former being presented to the external application and the latter requiring logic to be built on the external API Gateway to populate the internal API request with a different ClientID/Secret combination. With this, it becomes harder to have end-to-end traceability of the originating ClientID (unless this is mapped to a different header) and correlate the data together via the API analytics. We require the same ClientID/Secret to be leveraged across both implementations without having to provide a different ClientId/Secret combination to call the internal API.

Idea priority Medium
RFE ID 116517
RFE Product IBM API Connect
  • Admin
    Mar 4, 2022

    Hi, This can be achieved by using the APIC product APIs to set the client id and secret.