# On-behalf-of flow

Facts read 10 Nov 2026. Page reviewed 16 Nov 2026.

An authorization pattern where a service exchanges the token of the signed-in user for a new token aimed at a downstream resource, so the downstream call is judged against the user. The new token can carry both the user's identity and the calling agent's identity.

## An example, sourced

AWS documents the token exchange grant (On-behalf-of) for Amazon Bedrock AgentCore Gateway. The gateway exchanges the inbound user's access token for a new, scoped access token that targets a downstream resource. AWS says the exchanged token carries both the user's identity and the agent's identity, so downstream services can enforce fine-grained authorization at every hop without triggering additional consent flows.

## Why it matters here

This is the mechanism that keeps an agent from acting with more authority than the person asking. A reviewer should ask which tools use it and which fall back to the agent's own role. Flows like this are newer than plain service roles, so confirm the feature status in the provider page.

## Related pages

- [Identity propagation: meaning and an example](/glossary/identity-propagation/)
- [Model invocation logging: meaning and an example](/glossary/model-invocation-logging/)
- [CloudTrail data events: meaning and an example](/glossary/cloudtrail-data-events/)
- [All of them](/glossary/)

## Sources

- https://docs.aws.amazon.com/bedrock-agentcore/latest/devguide/gateway-outbound-auth.html (read 10 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://aiagentaccesscontrol.com/glossary/on-behalf-of-flow/
