Join our Newsletter — 33% off our NHI Course
Home› Glossary› Governance, Ownership & Risk› RFC 8693 Act Claim
Governance, Ownership & Risk

RFC 8693 Act Claim

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Governance, Ownership & Risk

The act claim is a JWT claim defined by RFC 8693 to represent delegation in a token. It identifies the acting party and can nest to show a chain of prior actors. This lets policy and audit systems distinguish impersonation from delegation and preserve who actually performed the request.

What the act claim represents in token exchange

The act claim is what gives a delegated token its accountability layer. In RFC 8693, it identifies the acting party so systems can preserve the distinction between the original subject and the party now exercising authority. That matters when requests are mediated, chained, or forwarded across services, because the token must still explain who actually did the work.

In practical terms, the claim supports delegation semantics rather than simple identity substitution. A token without an act chain can still authenticate a caller, but it may not preserve the full causal path of who initiated the request, who relayed it, and whether the current presenter is acting for someone else.

Why act chains matter for attribution and policy

Act chains help policy engines make finer distinctions than a single subject claim can provide. They let a system distinguish impersonation from legitimate delegation, which is critical for authorisation decisions, step-up checks, consent handling, and audit trails. This is especially important in distributed workflows where multiple services or agents can touch the same request.

The concept is also useful when the original actor and the current bearer are not the same entity. A nested act chain can preserve the sequence of prior actors, so downstream systems can answer not just who is calling now, but on whose authority and through which intermediaries.

For the standards background, RFC 8693 defines the token exchange model that the act claim belongs to, and the IETF Datatracker is the place to follow the RFC and related drafts.

How act differs from subject and may_act

The act claim is not a replacement for the subject of the token. The subject identifies the principal the token is about, while act identifies the party acting in the current hop or chain. That separation is what makes delegated flows auditable without collapsing the initiator, intermediary, and target into one ambiguous identity.

In deployments that also use may_act, the two claims serve different jobs. may_act expresses who is allowed to act, while act records who is actually acting in a specific token instance. Keeping those roles separate reduces confusion in policy logic and avoids treating every delegated token as if it were a direct impersonation token.

That distinction becomes even more valuable in cross-domain scenarios. When a token moves between trust domains, the claim structure can preserve the chain of authority instead of relying on informal log fields or application-specific conventions.

Where the act claim appears in modern delegated workflows

Act claims show up wherever one component performs work on behalf of another while still needing to expose provenance. Common examples include token exchange, on-behalf-of flows, service orchestration, federated access, and agent-mediated requests. In those patterns, the claim gives downstream systems enough context to enforce scoped access without losing attribution.

The same idea also helps when tooling or automation sits between the human initiator and the resource server. If a workflow passes through intermediaries, the act chain can show which intermediary transformed or relayed the request, which is often more useful than a flat “current user” model.

NHIMG’s OAuth Token Exchange and Delegation Guide is the most direct companion for readers who want the surrounding delegation model, including on-behalf-of flows and token downscoping.

Risk and Threat Considerations

Delegation chains create security value only if the chain stays trustworthy. If systems flatten, overwrite, or misread the act claim, they can lose the ability to tell delegation from impersonation, which weakens policy enforcement and can hide who actually initiated a sensitive action.

Failure mechanism: A compromised intermediary, confused-deputy pattern, or poorly implemented token exchange can cause the request to be executed under the wrong authority, or with the wrong attribution, especially when applications trust only the visible presenter and ignore the full chain.

Impact: The result can be privilege abuse, inaccurate audit evidence, broken approval logic, and weaker incident reconstruction, because security teams can no longer reliably trace which actor performed each step of the transaction.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

OWASP ASVS, NIST SP 800-53 Rev 5 and NIST SP 800-63 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
OWASP ASVSV8 — AuthorizationAct chains affect delegated access decisions and authorization context.
Recommendation — Validate delegated requests against explicit authorization context and preserve actor provenance in policy decisions.
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementToken exchange relies on controlled lifecycle and handling of bearer material.
AU-3 — Content of Audit RecordsAct claims preserve actor provenance needed in audit records for delegated actions.
AC-6 — Least PrivilegeDelegated tokens should constrain what the acting party can do on behalf of another.
Recommendation — Manage token lifecycle and handling so delegated credentials cannot be misused or silently extended. Record both the current bearer and prior actors so audits can reconstruct delegated activity. Scope delegated authority narrowly so the acting party can only perform the minimum required actions.
NIST SP 800-63Digital Identity GuidelinesThe claim supports federated identity and token-based delegation semantics in identity systems.
Recommendation — Align token handling with identity assurance and delegation semantics so identity context is not lost.

Practitioner Guidance

Why practitioners should care: If your platform uses delegated tokens, treat the act chain as a first-class security signal rather than a decorative JWT field. It should influence authorisation, audit, and investigation workflows whenever a request can be forwarded, proxied, or exchanged.

What to watch for: Be alert to implementations that only log the current bearer, strip nested actors during token transformation, or accept delegated requests without validating that the recorded authority matches the intended trust model. Those gaps often show up first as attribution failures, not obvious access-control errors.

Practitioner takeaway: A sound delegation design preserves both permission and provenance, so the system can answer not just “was this token valid?” but “who actually acted, and under what chain of authority?”

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.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org