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
Created by Guest
Created on May 7, 2026

EEM Admin API Access Token is strictly bound to a specific user identity

Token is strictly bound to a specific user identity
The token is strictly associated with the identity of the user who generated it, apparently including the audit trail. This has two issues - only this user has to specifically create it and manage it under his ID, it is not manageable by other users, and it causes CI/CD pipeline runs to effectively appear as actions of this specific user, which can be very misleading from an audit and compliance perspective.

It would therefore be highly desirable to allow users to generate a dedicated custom token (similar to GitHub access tokens) that clearly represents an application or automation rather than actions performed by an individual user (basically to imitate a service account or a system user). While it is the customer’s responsibility to properly secure such a token within their CI/CD platform, this approach would also support the desired governance model, where manual changes in production environments are restricted and deployments are performed exclusively via automation.

Idea priority High