The future of OAuth, AAuth & OIDC

Speakers

OAuth 2.0 and OpenID Connect power most single sign on flows and API access. They are here to stay, but they are evolving and may soon be joined by AAuth - Agent Authorization for the AI era.

The recommendations on how to do OAuth has evolved over the years. Addendum specs have been published that address new scenarios or improve existing flows. It is time to publish a new baseline that consolidates modern recommendations. The new spec is named OAuth 2.1.

With OpenID Connect being an extension to OAuth 2.0, those changes will of course affect OIDC too. More security hardening has also made OIDC suitable for high security environments, such as financial services and health care.

The MCP protocol for AI agents adopted OAuth for authorization, but it turns out that might not be the best fit. OAuth was never built for agentic identities. One possible answer is AAuth, a proposed standard that gives agents their own identity. But there are other alternatives discussed too.

Join me in this session where I'll walk you through hands-on demos on what modern OAuth and OpenID Connect looks like. I'll present what AAuth is as well as the other alternatives discussed for handling agentic identities.

An unhandled error has occurred. Reload 🗙