AIToday
Large Language ModelsAI Coding AssistantsAmazon AI BlogPublished: Nov 4, 2026, 04:00 JST

Amazon Bedrock AgentCore adds native on-behalf-of token exchange

Send on LINE
Amazon Bedrock AgentCore adds native on-behalf-of token exchange

3 Key Points

  1. What happened

    Amazon Bedrock AgentCore Gateway can now exchange a JWT for a ServiceNow-scoped token via Microsoft Entra ID's on-behalf-of flow, configured on the gateway target with no custom code.

  2. Why it matters

    ServiceNow applies the original user's permissions and audit trail instead of treating calls as the application itself, so agents no longer bypass user-level access controls.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The problem this addresses is a structural one for AI agents in the enterprise. When an agent calls an API on a user's behalf, the call can arrive at the downstream service as the application itself rather than the person who initiated the action. That erodes audit trails, sidesteps user-level access controls and undercuts least privilege. The fix is framed as identity propagation across the whole request chain.

The mechanics involve three parties. The AI agent application is protected by Microsoft Entra ID through an OAuth registration; AgentCore Gateway acts as a Model Context Protocol server between the agent and ServiceNow; and ServiceNow runs an inbound OAuth integration tied to Entra. Because the agent's token audience does not match what ServiceNow expects, the gateway bridges the gap by asking Entra for a new token scoped to the ServiceNow API connector. Entra first checks that the calling user consented to the delegation — meaning consent, not just configuration, sits on the path.

On the ServiceNow side, the exchanged token's preferred_username claim must map to an existing user, and limiting the auth scope to the Table API or whichever APIs the agent truly needs is advised. It also notes you can pair identity propagation with Amazon Bedrock Guardrails to filter harmful content and validate inputs and outputs. The same pattern is presented as applicable to other REST APIs protected by OAuth, so the ServiceNow walkthrough is arguably a template rather than a one-off integration.

FAQ
What does the on-behalf-of exchange actually change about the token?
The agent presents a JWT whose audience matches its own client ID. The gateway sends it to Entra with requested_token_use: on_behalf_of and receives a new token whose audience matches the ServiceNow API connector, with the original user's claims intact.
Do I need to write custom code for the token exchange?
No. You configure the token exchange on the gateway target and AgentCore Gateway performs it on each request. That removes the need for custom AWS Lambda interceptors.
Which gateway version supports native on-behalf-of?
You must create the gateway with MCP version 2025-11-25. Native OBO cannot be turned on for gateways created with earlier MCP versions.
Amazon AI BlogRead Original Article
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleGoogle Antigravity cuts drug discovery loop to about an hour