Skip to Main Content
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.

Status Under review
Created by Guest
Created on Jul 21, 2026

Take user session info from Teams activity objects, to enable usage of user session tokens for permissions

I understand from the documentation that Member credentials are not supported on downstream channels, such as MS Teams which are we are interested in using.

When a user accesses an agent via Teams, there is no capability to sign in via the OAuth connector as is on the WatsonX Orchestrate test chat. This makes sense because it would be expected that the user's session, referenced in the Activity Objects between Teams and WXO would be already stored and could be usable for identifying users and determining permissions.

However, this is not stored within a connections object, and therefore we cannot access that session information. This code works for getting the access token from an OAuth session within the WXO test chat:

def _get_mcp_client() -> Client:
"""Creates an MCP client with Bearer token authentication from the OAuth connection.

Zero-trust model: OAuth token validated on every request by the MCP server.

Returns:
Client: FastMCP client configured with the user's OAuth token
"""
oauth_conn = connections.oauth2_auth_code(OAUTH_APP_ID)
token = oauth_conn.access_token

print(f"[MCP] Connecting to: {MCP_SERVER_URL}")
print(f"[MCP] Bearer token preview: {token[:20]}...")

transport = StreamableHttpTransport(MCP_SERVER_URL)
return Client(transport, auth=BearerAuth(token=token))

However, that oauth2_auth_code connection object is inaccessible in Teams, and therefore we cannot pass the user details anywhere to provide context for permissions. If a user chat requests an OAuth sign in normally in the WXO test chat, it shows nothing in Teams to prompt the user, but should instead have a way to access these credentials.

Idea priority Urgent