OpenID Foundation Warns That AI Agents Are Breaking Identity Management

OpenID Foundation: Identity Management for Agentic AI [pdf]

The OpenID Foundation's new whitepaper argues that today's OAuth 2.1 and OpenID Connect frameworks work for simple, single-domain AI agents but fail for cross-domain, asynchronous, or highly autonomous ones. It identifies urgent gaps: agent identity fragmentation, user impersonation, consent fatigue, recursive delegation, and browser agents bypassing API controls. The report calls for interoperable identity profiles, explicit on-behalf-of delegation, and new programmatic verification for trustworthy autonomy.

Agents controlling visual interfaces directly (or via MCP into browser orchestrators) bypass all traditional API-based authorization controls. Protecting the open web from lockdown will require robust authentication of web bots or web agents.
  1. iamjake648

    How does this releate (or not) to Okta/Auth0's XAA, Identity Assertion JWT Authorization Grant? I'm struggling to follow.

    https://auth0.com/docs/ai-agents-mcp/cross-app-access

    https://datatracker.ietf.org/doc/draft-ietf-oauth-identity-a...

  2. udbhavs

    I've been working in this space with a small team that is also trying to solve this with open standards. There are many emerging protocols/standards and many dimensions to consider. I have a list of 50 standards using different primitives and flows, but it's hard to see which ones will stick around at this point.

    You could split use cases by scope. One is internal organization and IAM cases, which makes it easy for you to use a centralized identity provider (IdP) to issue some sort of token grant access to an app.

    Use cases where you don't want to fix an IdP, like payments or verifying the someone's credentials before giving access on the open web, get more involved. You could have multiple valid IdPs, reputation / claims linked to IDs (since being on the IdP itself is no longer sufficient for an app to let the actor through), inheriting authority through multiple hops (giving your authorization to someone), enforcing narrowing permissions for those use cases, handling revocations. And then there's also the matter of being compatible with other emerging standards that are coming up (eg. A2P for agent payment authorization).

    We settled on the core primitives of W3C DIDs for identity, Verifiable Credentials for delegations, and StatusList bitstrings for revocations as the "minimal set of ingredients" that address all the above. They are all open standards. DIDs are particularly cool because you can have them bound to passkeys, web domains through existing PKI, and even ledgers. […]

  3. juanre

    I wrote a solution for this, and it has been working across several organizations for some months now. I run it as a public service at https://awid.ai but I would love to offload it to a foundation.

    - OSS (https://github.com/awebai/aweb/tree/main/awid)

    - Trust rooted in the DNS.

    - Multiple registries supported.

    - did, verifiable stable identities.

    - Certificate-based teams.

    It is being a very interesting project so far. It's at the core of my https://aweb.ai which enables agents to communicate globally, and it makes it possible to build really simple agent-first tools where auth is just a matter of validating a certificate.

More from this day

2026-10-01