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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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...
Do not place IBM confidential, company confidential, or personal information into any field.