Cross Domain · security identity
OAuth 2.1
OAuth 2.1 is a consolidation of OAuth 2.0 and the extensions and security practices that have become standard since 2012. It is not a new protocol — it folds the Security Best Current Practice into the core, makes PKCE mandatory for authorization code flows, and removes the implicit and resource owner password credentials grants entirely.
Also known as OAuth 2.1.
Providers that carry OAuth 2.1 0
No provider in the catalog carries this standard as a tag yet. That is a statement about the catalog's tagging, not about adoption: a provider that implements OAuth 2.1 and says so in its APIs.json profile appears here on the next build. Add or correct a listing.
Read from the API Evangelist standards directory. Provider links come from the catalog's own identity tags and are rebuilt nightly. If this page is wrong about a standard or a provider, say so.