Skip to content
IAM Insights

Explainers · Glossary

Step-up authorization

step-up authorization flow · step-up auth · incremental authorization

Requesting additional OAuth scopes at runtime, on top of a token a client already holds, when an operation needs more permission than was originally granted — rather than restarting the whole authorization flow from scratch.

In our briefings

The claim each of the newest briefings on Step-up authorization would have you leave with.

  1. Across its eight panels the summit settles one rule and names one unsolved problem. The rule is to delegate, never impersonate: an agent gets its own identity, the person's authority passes to it by token exchange (an OAuth step that swaps one token for another) at each hop from one party to the next, and the agent may do only what every identity in the chain is allowed to do. The unsolved problem is the second hop. Once an agent starts other agents, no shipping standard carries the person who started the job and the limits added along the way. An Amazon engineer works on the transaction-token draft, a draft standard for short-lived tokens that carry a request's context between services. He says the record of the chain is optional and survives only if the HTTP header has room. His own group is drafting a way for a parent agent to issue its children's identities, the opposite of the rule every other panel states. Uber built its own record of the chain and published it; nobody on the stage had built one.

    Eight panels agree an agent acts for a person, never as that person. When agents hand work to other agents, nobody had an answer.BI-FIND-2026-0469

  2. The record of who delegated to whom is optional in practice, and what decides whether it survives is room in the HTTP header. Amazon principal engineer Ashay Raut, who works on the OAuth transaction-token draft, says an implementer doing token exchange may keep the actor chain in the token or drop it, and that a bank or a hospital that needs it should keep it somewhere else and decide for itself where. That matches the text: RFC 8693 treats earlier actors as informational only. Uber carries the full chain in every token; nothing obliges the next implementer to.

    Keeping an agent's delegation chain is optional, and room in the HTTP header decides whether it survivesBI-FIND-2026-0239

  3. As of the 28 July 2026 revision, an MCP client is an OAuth 2.1 client and an MCP server is an OAuth 2.1 resource server, and that is the whole identity model. Authorization is optional; HTTP transports SHOULD use it, and 'implementations using an STDIO transport SHOULD NOT follow this specification, and instead retrieve credentials from the environment'. The authorization server is out of scope. There is no actor claim, no on-behalf-of flow, no token exchange and no transaction-token profile: nothing in the token says whom the agent is acting for, which is what the Identiverse summit panel meant by 'not a policy system' and what WorkOS meant by the gateway being undefined. Anything of that kind is routed to the new extension model, optional and additive, in a separate repository. This page is the baseline against which the summit's forecast, that the specification gains a delegated-identity mechanism within a year, will be graded.

    MCP's authorization spec makes the agent a plain OAuth client and leaves delegation to an extensionBI-FIND-2026-0189

Cited in 4 briefings

Every briefing that discusses this term, newest first.

  1. Eight panels agree an agent acts for a person, never as that person. When agents hand work to other agents, nobody had an answer.

    Conference · · Las Vegas · June 2026, a one-day summit track inside Identiverse 2026; the eight panels were published as podcast episodes between 18 August and 7 September 2026

  2. Keeping an agent's delegation chain is optional, and room in the HTTP header decides whether it survives

    Podcast · · The Non-Human & AI Identity Podcast · NHI & AI Identity Summit : The New NHI Risk Reality · Aug 26, 2026

  3. MCP's authorization spec makes the agent a plain OAuth client and leaves delegation to an extension

    Article · · Model Context Protocol project · Jul 28, 2026

  4. Google DeepMind wants agent authority to narrow at every hand-off, and misreads MCP's scopes on the way

    Paper · · arXiv · Nenad Tomašev et al. · Feb 12, 2026