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 Delivered
Workspace API Connect
Created by Guest
Created on Jul 30, 2018

Can we retain the same Client ID and Client Secret Key to all environments(DEV/INT/QA) in Developer Portal?

We are trying to use same client ID and Client secret across all the environments.

Idea priority High
RFE ID 123042
RFE URL
RFE Product IBM API Connect
  • Guest
    Reply
    |
    Aug 29, 2018

    We need a way to provide CLI to import/export Client ID, Client Secret and Product Subscriptions. It's not just for DevOps usage but also for product upgrade and migration; migrating from APIC 5.x to APIC 2018; running a parallel n+1 version to allow application to gradually move over; or creating a live DR environment in case of disaster recovery.