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 Delivered
Created by Guest
Created on Apr 17, 2025

RELATED IDEAS

3rd-party agent authentication/authorization

WxO has no mechanism to keep authentication smoothly with outside agents.

It is applicable to both Talent & Finance use cases:

Currently on Talent side we have the following issue:

  • We build our agent using LangGraph & Langchain outside WxO.

  • WxO call this agent using RESTful method, such as /chat/complete. The agent needs to know what’s the current user, and based on user credentials , execute the action, such as f.e. ‘ list my job reqs’.

Currently WxO does not support such capability, and when using AI Agent configuration, we can not pass the parameter to the agent that will help to identify the user who is sending such request. Parameter can be token, or pure text at least ( email address of the logged user) passed into api (either as a header or body context). To have proper security mechanism - it should be security token.

Idea priority Urgent
  • Post comment
  • Admin
    Laurent Tillette de Clermont-Tonnerre
    Oct 7, 2025

    Passing of user identity/SSO token in context to external agents, is coming in 4Q, will that address more of the present need?

    More in 1Q on Agent Identity & Authentication.

    1 reply
  • Guest
    Jun 18, 2025

    This be the first step. Next step - JIT/JEA

    1 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.