A token or session pattern where one identity acts for another while preserving evidence of delegation. For agents, the value is not just access propagation. It is the ability to show that the action was performed under a specific authority and within a specific scope.
What On-Behalf-Of Flow Does
On-behalf-of flow is a delegation pattern, not just a token handoff. It lets one identity obtain a token that represents authority to act for another identity, so the receiving system can distinguish delegation from direct impersonation and preserve the evidence needed to explain who authorised the action and under what scope.
That distinction matters because the security question is not only whether the caller is authenticated, but whether the resulting action can be traced to the right subject, bounded by the right consent or policy, and constrained to the permissions the actor was meant to inherit. It is a common control point in token exchange, service-to-service access, and agent-mediated workflows.
How Delegation Differs From Simple Credential Forwarding
Simple credential forwarding usually moves a bearer credential downstream and obscures the acting party. On-behalf-of flow instead preserves an explicit delegation relationship, often using a token exchange pattern, so the downstream service can see both the original subject and the actor that requested the token.
That structure reduces ambiguity in audit and policy decisions. A system can still reject or narrow access when the delegated action exceeds the permitted scope, even if the caller is a trusted intermediary. In practice, this is what makes on-behalf-of useful for APIs, brokers, gateways, and orchestration layers that need to perform work for a user or another service without collapsing the two identities into one.
The difference also affects trust boundaries. With forwarding, every hop tends to inherit the same standing authority. With on-behalf-of, the authority is intentionally re-issued for a narrower purpose, which makes the chain of responsibility easier to reason about and easier to govern.
Authority, Scope, and Traceability
The core design goal is delegated authority with attribution. The token should express who is acting, who is being represented, and what the actor may do in that delegated context. That lets policy decisions key off the delegated relationship rather than treating the request as if it originated from the end subject directly.
For practitioners, the important implication is that scope must survive the exchange. If a delegated token is too broad, the flow becomes a privilege-amplification path instead of a controlled delegation mechanism. If it is too opaque, downstream services lose the ability to validate the actor, the subject, and the intended audience of the token.
For a practical reference on how this pattern is formalised, OAuth Token Exchange and Delegation Guide explains RFC 8693, actor and subject tokens, and downscoping in the context of delegated access.
Where It Shows Up in Modern Systems
On-behalf-of flow is most valuable when a middleware component, workflow engine, or AI agent needs to act with delegated authority rather than its own standing rights. The pattern is common in API mediation, cross-domain integrations, and agentic systems that need to prove they are operating under a specific sponsor, user, or upstream service context.
That is why delegated token handling is often discussed alongside service authentication, workload identity, and agent identity governance. The token is not merely a secret used to gain access; it is a carrier for delegation evidence. If the system cannot preserve that evidence, downstream authorisation and investigation become much harder.
For a broader view of how non-human actors authenticate and present delegated authority, NHI Authentication Guide covers client credentials, mTLS, workload identity federation, and token exchange in service-to-service contexts.
When the flow involves autonomous software acting for a person or another system, the identity model also has to show which authority was delegated and which actions were within scope. Agentic AI Identity Guide addresses that delegation, registration, and retirement lifecycle for agents.
Risk and Threat Considerations
On-behalf-of flow creates risk when delegation evidence is weakened, discarded, or too broadly granted. If a system cannot preserve the subject, actor, and scope of the exchange, an intermediary can gain more authority than intended, and downstream services may treat delegated actions as if they were directly authorised by the original subject.
Failure mechanism: Token exchange that omits audience restrictions, scope narrowing, or actor attribution can turn delegation into privilege amplification, confused-deputy behaviour, or unauditable impersonation.
Impact: The result can be unauthorised actions, poor forensic attribution, excessive downstream trust, and a higher chance that a compromised intermediary can misuse delegated access across multiple systems.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and NIST SP 800-63 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Token exchange and delegated credentials rely on controlled lifecycle management of authentication material. |
| AC-6 — Least Privilege | On-behalf-of flows should narrow delegated authority to the minimum needed for the task. | |
| AU-3 — Content of Audit Records | Delegation evidence must preserve actor, subject, and scope for traceable actions. | |
| Recommendation — Manage delegated tokens with controlled issuance, renewal, revocation, and expiry. Constrain exchanged tokens to the least privilege required for the delegated action. Log the actor, subject, and scope of delegated actions in audit records. | ||
| NIST SP 800-63 | Federation — Federation | The term depends on token exchange and delegated assertions across trust domains. |
| Recommendation — Use federated assertions and token exchange to preserve delegated authority across domains. | ||
Practitioner Guidance
Why practitioners should care: The control objective is not just to make requests work, but to make delegated requests provable. If your platform uses on-behalf-of flow, make sure the token exchange design preserves the original subject, the acting party, and the intended audience in a way downstream services can enforce and auditors can interpret.
Common misunderstanding: Teams sometimes treat on-behalf-of as a convenience feature for passing access through layers. In practice, it is a governance mechanism, because the security value depends on whether each hop can validate delegation, not merely relay a credential.
Practitioner takeaway: Use the flow only when you need delegated authority with traceability, and keep the exchanged token narrower than the caller’s standing rights.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org