Skip to Main Content
Digital Business Automation Ideas


This is an IBM Automation portal for Digital Business Automation 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.


Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):
  • Cloud Pak for Business Automation - including Business Automation Studio and App Designer, Business Automation Insights

  • Business Automation Workflow (BAW) - including BAW, Business Process Manager, Workstream Services, Business Performance Center, Advanced Case Management

  • Content Services - FileNet Content Manager

  • Content Services - Content Manager OnDemand

  • Content Services - Daeja Virtual Viewer

  • Content Services - Navigator

  • Content Services - Content Collector for Email, Sharepoint, Files

  • Content Services - Content Collector for SAP

  • Content Services - Enterprise Records

  • Content Services - Content Manager (CM8)

  • Datacap

  • Automation Document Processing

  • Automation Decision Services (ADS)

  • Operational Decision Manager

  • Robotic Process Automation

  • Robotic Process Automation with Automation Anywhere

  • Blueworks Live

  • Business Automation Manager Open Edition

  • IBM Process Mining


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 Jul 21, 2026

Native validation of third-party IdP tokens for system-to-system (no-user) calls to CP4BA/BAW REST APIs using OAuth client_credentials

Problem / gap: CP4BA IAM (Zen) currently expects an IdP -> IAM -> Zen token exchange and requires a valid AD/directory user in the token subject before it will authorise a call. It cannot natively validate arbitrary external (third-party) IdP JWT tokens, and it cannot authorise system-to-system requests where there is no user in the token subject. This blocks a common integration pattern where external systems call BAW REST resources running on CP4BA.

Customer scenario : 
An enterprise OIDC provider is configured as the IdP for CP4BA IAM. External systems need to obtain a token via grant_type=client_credentials and use it to authorise REST calls into BAW. 
Three scenarios need to be supported: 
(1) a user authenticating via an external IdP calling CP4BA with a user JWT (sub = user digital id)
(2) staff authenticating via an external IdP calling CP4BA with a staff JWT (sub = staff UPN)
(3) system-to-system calls with no user, using client_credentials (client id + scope only).

Current workaround and its limitation: The Zen custom authentication handler can call an external validator service and use a template/regex mapping to extract a username from the external token response, after which the gateway internally generates and caches a Zen token so backend services never see the external token. 

However, this requires the customer to host their own validator or supply the template/regex mapping, and it does not cleanly cover the no-user client_credentials case because BAW REST APIs are role-based and expect a user with the right roles.

Requested capability: 
Provide standardised, native support in the platform for accepting and validating third-party IdP JWT tokens - including OAuth client_credentials (no-user) tokens - and mapping them to an authorised identity/scope, without requiring a customer-hosted validator. 

Validation should enforce defined/acceptable scopes and cryptographic verification so that only authenticated, scoped tokens are accepted. (Client Credentials Grant).

Idea priority Urgent