Create

Sign in to ReadmeX

or

How we handle your data: Privacy Policy

ReadmeX

Your AI reading companion

What would you like to catch up on?

Pick a briefing, or ask your own question.

Your community and people briefings stay personal to you.

Story

AgentCore Gateway adds native Entra ID token exchange

AI summary

An AWS technical walkthrough shows how Amazon Bedrock AgentCore Gateway can natively perform an on-behalf-of token exchange with Microsoft Entra ID. The configuration lets an AI agent call the ServiceNow REST API while preserving the calling user’s identity and removes the need for a custom AWS Lambda interceptor; the gateway performs the exchange on each request. AWS says the pattern can also be applied to other OAuth-protected REST APIs and paired with Amazon Bedrock Guardrails. Native on-behalf-of support requires AgentCore Gateway to use MCP version 2025-11-25 and cannot be enabled for gateways created with earlier MCP versions.

In-depth insight

The walkthrough says preserving identity throughout the request chain supports user-level access controls and preserves audit trails, while native token exchange eliminates custom code that would otherwise need separate maintenance. The capability was not independently verified in the supplied source.

AI agents that interact with enterprise APIs on behalf of users need to maintain user identity throughout the request chain. Without identity propagation, API calls arrive at downstream services as the application itself rather than the user who initiated the action. This breaks audit trails, bypasses user-level access controls, and violates the principle of least privilege.

Amazon Bedrock AgentCore is a platform to build, connect, and optimize agents at scale, with any framework or model. This post shows how to configure AgentCore Gateway, a capability of Amazon Bedrock AgentCore, for an on-behalf-of (OBO) token exchange with Microsoft Entra ID. An AI agent can then call the ServiceNow REST API while preserving the calling user’s identity. You configure the token exchange on the gateway target, and AgentCore Gateway performs the exchange on each request. The pattern can be applied to other REST APIs protected by OAuth.

In production, you can additionally pair identity propagation with Amazon Bedrock Guardrails to filter harmful content and validate the agent’s inputs and outputs.

Solution overview

The architecture involves three key components connected through AgentCore Gateway:

#Amazon Bedrock AgentCore Gateway#Microsoft Entra ID#ServiceNow REST API#Amazon Bedrock Guardrails#AWS Lambda#Model Context Protocol

Original · 10 min readRead the original
Group chat

No comments yet. Start the conversation.