ServiceNow on-behalf-of token exchange with Bedrock AgentCore Gateway
Learn how to configure Amazon Bedrock AgentCore Gateway for an on-behalf-of (OBO) token exchange with Microsoft Entra ID, so an AI agent can call the ServiceNow REST API while preserving the calling user's identity. AgentCore Gateway performs the exchange natively, with no interceptor Lambda or custom code.
First seen by Oriel on .
AI summary
The post explains how to configure Amazon Bedrock AgentCore Gateway to exchange Microsoft Entra ID tokens on behalf of users, preserving their identity and permissions in ServiceNow API calls.
- The flow exchanges an agent-scoped JWT for a ServiceNow API token while retaining the original user’s claims, allowing ServiceNow to apply that user’s permissions.
- Setup requires separate Entra application registrations for the agent and ServiceNow API connector, plus a ServiceNow inbound OAuth integration and OIDC claim mapping.
- AgentCore Gateway’s native OBO support requires MCP version 2025-11-25 and a target configured with the ServiceNow scope and requested_token_use:on_behalf_of parameter.
- The gateway performs the exchange on each request and forwards the token to ServiceNow without custom exchange code.
- The example exposes ServiceNow’s Table API through an MCP tool; the article also recommends considering Amazon Bedrock Guardrails for filtering content and validating agent inputs and outputs.
#amazon bedrock agentcore #microsoft entra id #servicenow #oauth
Generated by gpt-5.6-sol. Check the original for details.
Aliases
| Source | External ID | URL |
|---|---|---|
| AWS Machine Learning Blog | 1350dc3292e99da0becbb3e875f11092aaa597f1 | https://aws.amazon.com/blogs/machine-learning/servicenow-on-behalf-of-token-exchange-with-bedrock-agentcore-gateway/ Read discussion |