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 Future consideration
Workspace API Connect
Created by Guest
Created on May 11, 2022

Allow a "service ID" to work in v10 API Connect RI

Similar to APICONN-I-474 (which I can't see, so I can't vote on).


I would like to NOT use a person ID in IAM to access the APIs that control my API Reseved Instance. When we are doing system to system interactions, configuration, polling analytics, etc, the only way to interact with v10 RI is to use a real person's IAM account.


For On prem v10, you could register an application, but you can't do that anymore in v10 RI.


The other option, which is still IAM based, is to use "Service IDs", but that does not function with API Connect.


See ticket CS2584389 for lots of info and back and forth...

Idea priority Urgent
  • Admin
    Nathan Ziemann
    Aug 8, 2022

    We are looking at this and would approach using the same API Connect software approach allowing registration of client apps, instead of the approach taken with service_ids through IAM. This would result in consistent experience for software or SaaS. We are considering this for future.

  • Admin
    Nathan Ziemann
    Jul 26, 2022

    We are uncertain if this is possible given how the required IBM Cloud IAM Service is designed. We will discuss with them and if possible we will evaluate options for future enhancement. Moving to future consideration.

  • Guest
    May 17, 2022

    I worked the subject ticket CS2584389 - I've seen similar requests (hence APICONN-I-474).

    Not sure how it can be done - but Service ID is the design pattern for IAM service access.