Preserving User Identity in ServiceNow Calls with Bedrock AgentCore Gateway OBO Token Exchange
AI assistants · Enterprise AI
AWS demonstrates configuring Amazon Bedrock AgentCore Gateway to perform on-behalf-of (OBO) token exchange with Microsoft Entra ID. This allows AI agents to interact with ServiceNow REST APIs while maintaining the invoking user's identity, preserving access controls and audit trails.
Amazon Bedrock AgentCore supports native on-behalf-of (OBO) token exchange via AgentCore Gateway and Microsoft Entra ID, ensuring user identity is propagated when AI agents make downstream API calls to enterprise platforms such as ServiceNow. Without identity propagation, downstream API requests appear as originating from the agent application itself rather than the requesting user, violating least privilege and disrupting audit logs. In this architectural pattern, an AI agent authenticates with a JWT token, which AgentCore Gateway exchanges via Entra ID using the OBO flow for a new token tailored to the ServiceNow API connector. ServiceNow then maps the token's preferred_username claim to enforce user-specific permissions. The integration requires configuring application registrations in Entra ID, an inbound OAuth OIDC integration in ServiceNow, and selecting MCP version 2025-11-25 on AgentCore Gateway.
Key takeaways
- Amazon Bedrock AgentCore Gateway supports on-behalf-of token exchange with Microsoft Entra ID to preserve end-user identity during downstream ServiceNow REST API calls.
- Identity propagation prevents agents from bypassing user-level permissions and breaking enterprise audit trails across external service invocations.
- The setup requires two Entra ID application registrations, ServiceNow inbound OAuth integration mapping user claims, and AgentCore Gateway set to MCP version 2025-11-25.
Source：AWS Machine Learning Read the original ↗
Prepared, checked and automatically published by AI; not individually reviewed by a human.