Skip to content
IAM Insights

Explainers · Glossary

ZeroID

Highflame ZeroID

Highflame's open-source identity service for AI agents: each agent has its own identifier, and delegation narrows scope at each hop using OAuth token exchange.

reference →

In our briefings

The claim each of the newest briefings on ZeroID would have you leave with.

  1. The IETF datatracker shows that the IESG approved OAuth Identity and Authorization Chaining Across Domains (draft-ietf-oauth-identity-chaining) as a Proposed Standard on 22 June 2026, and that it has been in the RFC Editor's queue since that day. Revision 17, the text we read, was posted on 19 July 2026 during that editing. Its authors are Arndt Schwenkschuster and Pieter Kasselman of Defakto Security, Kelley Burgin of MITRE, Mike Jenkins of NSA-CCSS, Brian Campbell of Ping Identity and Aaron Parecki of Okta. Campbell co-wrote RFC 8693 and RFC 7523, the two RFCs the draft combines, and Parecki co-wrote RFC 9728, one of the ways it names for finding the other domain's authorization server. The working group's write-up for the IESG lists implementations, among them Keycloak 26.5 and Okta's. Two other drafts we have read point to it: the transaction-tokens draft leaves crossing domains to it, and the AI agent authentication draft says cross-domain access SHOULD use identity chaining.

    OAuth's draft for crossing trust domains is approved for publication and never says agentBI-FIND-2026-0184

  2. A delegated mission's authority must be a subset of the parent's, McGuinness argues, and OAuth token exchange (RFC 8693) does not guarantee it. Token exchange carries the delegation, but he calls enforcing the narrowing implementation-dependent and not a protocol guarantee. He writes that in production token exchange deployments today, child tokens routinely inherit the parent's full scope unless the implementation explicitly narrows them, so agents compound a failure that OAuth delegation already has. A child agent may also run in a different runtime or expose weaker telemetry, so authority that is narrower on paper can be less governable in practice. He proposes that the mission's state owner rate each hop's trust quality, meaning how well that hop can be observed and checked, and give a low-rated child a more conservative budget. For a sub-agent an orchestrator spawns at runtime, he says the state owner must still issue its authority, but asks what triggers that issuance. Our briefing on Uber's production design found a token chain that records each agent hop without describing any narrowing. Our briefing on Highflame's open-source ZeroID found narrowing by scope intersection offered as an explicit step.

    OAuth token exchange does not guarantee a sub-agent stays inside its parent's accessBI-FIND-2026-0228

  3. The co-chair of the OpenID Foundation's AI identity group does not think agents need a new identity system. Tobin South's position is that web login, SAML, SCIM and the identity provider's handling of agents each need a modest upgrade, that no single fix exists, and that anyone who says otherwise is selling a product. He points out that identity providers already let a company declare an agent, tie it to a person and switch it off. The IETF's agent-authentication draft opens with the same complaint, that the field keeps reinventing mechanisms it already has.

    An OpenID Foundation co-chair says AI agents need modest upgrades to today's identity systems, not a new oneBI-FIND-2025-0088

›Cited in 6 briefings

Every briefing that discusses this term, newest first.

  1. OAuth's draft for crossing trust domains is approved for publication and never says agent

    Draft · · IETF OAuth Working Group · Arndt Schwenkschuster et al. · Jul 19, 2026

  2. OAuth token exchange does not guarantee a sub-agent stays inside its parent's access

    Article · · Control Plane by Karl McGuinness · Karl McGuinness · Mar 18, 2026

  3. An OpenID Foundation co-chair says AI agents need modest upgrades to today's identity systems, not a new one

    Podcast · · Identity at the Center · #390 - Identity Management for Agentic AI with Tobin South · Dec 8, 2025

  4. Most of the work in Sierra's MCP gateway was identity: who each agent acts as and what it may reach

    Article · · Sierra Engineering · Mihai Parparita · Jul 22, 2026

  5. 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

  6. Highflame's open-source ZeroID narrows an agent's token at every hop, a step we did not find in Uber's write-up

    Article · · Highflame (GitHub) · Sep 25, 2026

Related terms

What appears alongside ZeroID in the same briefings.

HighflameOAuth Token ExchangeSPIFFE