Shape the future of IBM watsonx Orchestrate

Start by searching and reviewing ideas others have posted, and add a comment (private if needed), vote, or subscribe to updates on them if they matter to you.

If you can't find what you are looking for, create a new idea:

  1. stick to one feature enhancement per idea

  2. add as much detail as possible, including use-case, examples & screenshots (put anything confidential in Hidden details field or a private comment)

  3. Explain business impact and timeline of project being affected

[For IBMers] Add customer/project name, details & timeline in Hidden details field or a private comment (only visible to you and the IBM product team).

This all helps to scope and prioritize your idea among many other good ones. Thank you for your feedback!

Specific links you will want to bookmark for future use
Learn more about IBM watsonx Orchestrate - Use this site to find out additional information and details about the product.
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.

Add idea Subscribe
Status Submitted
Created by Guest
Created on Aug 27, 2026

RELATED IDEAS

Support End-User Identity Propagation for Downstream Authorization and Auditing in Integrations Using CPI middleware

Watsonx Orchestrate currently supports Team and Member credential models for authenticating tools and connectors.

When a watsonx Orchestrate agent invokes a custom tool or prebuilt SAP connector and the request is routed through SAP CPI (SAP Integration Suite) before reaching SAP S/4HANA, there is no documented end-to-end mechanism to propagate the authenticated end-user identity to the downstream system.

As a result, SAP authorization checks and audit records are often evaluated against a shared technical account rather than the actual user who initiated the request through the agent.

The request is for a supported identity propagation approach that allows the originating Orchestrate user identity to be carried through CPI to SAP.

This would enable downstream systems to:

  • Apply existing user-specific authorization checks.
  • Record the actual requesting user for auditing and traceability.
  • Support both custom tools and prebuilt connectors used by Orchestrate agents.
Idea priority High
  • Post comment
  • Guest
    Sep 7, 2026

    Adding some information the development has requested.

     

    1. What is the exact target system: SAP S/4HANA, SAP SuccessFactors, or both?

    - SAP S/4HANA.

     

    2. What authentication or identity propagation mechanisms does the target SAP system support for this integration?

    - No identity propagation is currently used. For authentication, we use Basic Auth.

     

    3. Does it support a user-specific token/assertion, such as JWT, SAML bearer assertion, OAuth token exchange, or another principal propagation mechanism?

    - No; the connection for the pre-built tools is currently configured with Basic Auth end-to-end (Orchestrate -> CPI -> SAP), with no token-based or assertion-based propagation mechanism in place.

    WxO → CPI => Basic Auth 

    CPI → SAP => Basic Auth

     

    4. What identity provider or issuer does SAP currently trust for authenticating these users?

    - No identity provider is currently configured for this.

     

    5. Is the WxO user's identity expected to correspond directly to an existing SAP user, for example through email, username, or another identifier?

    - No, this has not been configured. On the Orchestrate side as well, we are currently using a shared identity rather than individual user mapping.

     

    6. Can the existing SAP/CPI setup establish trust with an external identity issuer, or does it require the caller to authenticate using SAP-native user credentials?

    - There is no current setup to establish trust with an external identity issuer; the caller authenticates using SAP-native credentials via Basic Auth.

    Reply

By clicking the "Post Comment" or "Add Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not include IBM confidential, company confidential, or personal information in any field.
Having problems accessing this portal? Describe the problems in an email to ideasibm@us.ibm.com.