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:
Post your ideas
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive a notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
If you encounter any issues accessing the Ideas portal, please send email describing the issue to firstname.lastname@example.org for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.
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.