OAuth 2.0
Snapshot
The Question this Spec Answers
Identity & Status
| Field | OAuth 2.0 |
| Full name | The OAuth 2.0 Authorization Framework , commonly “OAuth 2.0” or “OAuth 2.” |
| Type | A standards-track authorization framework and protocol family, published as RFC 6749; it is not itself an authentication protocol. |
| Authority type | De-jure. RFC 6749 is an IETF Standards Track RFC produced through the IETF OAuth Working Group, with public drafts, mailing-list archives, named chairs, IESG review, and an RFC editor named on the cover. |
| Created by | The first public OAuth 2.0 draft named Eran Hammer-Lahav of Yahoo! as editor, David Recordon of Facebook , and Dick Hardt as authors; it also credited substantive participation by Allen Tom of Yahoo!, Brian Eaton of Google, Brent Goldman and Luke Shepard of Facebook, Raffi Krikorian of Twitter, and Yaron Goland of Microsoft. |
| Created year | 2010 . The first public OAuth 2.0 Internet-Draft was dated April 22, 2010. |
| Original publisher | Internet Engineering Task Force , through its Internet-Draft repository; the initial document was an individual Internet-Draft rather than an adopted working-group document. |
| Final RFC editor | Dick Hardt , affiliated with Microsoft on RFC 6749’s cover. |
| Maintained by | The active IETF Web Authorization Protocol Working Group ; its current chairs are Hannes Tschofenig and Rifaat Shekh-Yusef, its secretary is Michael B. Jones, and its assigned Security Area Director is Deb Cooley. |
| Current version | RFC 6749 , published October 2012, remains the core OAuth 2.0 framework; it has been updated by RFC 8252, RFC 8996, and RFC 9700. The in-progress consolidation and likely successor is OAuth 2.1 draft-ietf-oauth-v2-1-17 , dated October 30, 2026. |
| Lifecycle stage | RFC 6749 is an IETF Proposed Standard and remains active, but important portions of its original operating envelope have been superseded by Best Current Practice guidance. OAuth 2.1 remains an active Working Group Internet-Draft with a December 2026 milestone for submission to the IESG. |
| License | Copyright is held by the IETF Trust and identified authors, subject to BCP 78 and the IETF Trust Legal Provisions; extracted code components use the Simplified BSD terms specified by those provisions. This is not a generic MIT or CC-BY publication license, and the document license does not itself grant patent rights; IETF patent disclosure operates through BCP 79. |
| Canonical URL | RFC 6749 — The OAuth 2.0 Authorization Framework . |
Why It Matters
What it unlocks
| Unlock | Strategic significance |
| Delegation without password transfer | A user can approve limited third-party access while the authorization server retains control of the user’s primary credentials. This separates an integration’s authority from possession of the account password and permits access to be scoped, expired, or revoked independently. |
| A common authorization architecture across client types | OAuth 2.0 established reusable roles and flows for server-side web apps, browser clients, installed applications, limited-input devices, and machine clients; Google’s implementation alone documents web-server, client-side, installed, device, and service-account scenarios. |
| Portable identity and sign-in layers | OpenID Connect uses OAuth 2.0 as its authorization substrate and adds interoperable end-user authentication and profile claims, turning OAuth’s delegation machinery into the base for widely deployed federated sign-in. |
| Regulated, consent-driven data portability | UK Open Banking adopted FAPI—a hardened OAuth profile—for bank APIs, enabling customers and SMEs to authorize third-party financial services without giving those services bank passwords. |
| Extensible high-assurance security | PKCE, PAR, DPoP, mTLS, JAR, authorization-server metadata, and FAPI can harden the generic framework for interception resistance, request integrity, sender-constrained tokens, discovery, and high-value APIs. |
| A reusable authorization layer for new protocol families | MCP’s HTTP authorization model now requires OAuth Protected Resource Metadata and uses OAuth discovery to connect clients, protected tool servers, and authorization servers. |
Impact it has had
| Impact | Evidence and consequence |
| OAuth 1.0 was displaced as the mainstream baseline | RFC 6749 explicitly obsoleted RFC 5849, and providers such as Atlassian and X have continued moving integrations from OAuth 1.0a to OAuth 2.0. |
| Password-sharing and screen scraping lost legitimacy | Modern open-banking APIs use tokenized OAuth access rather than handing raw bank credentials to aggregators; UK guidance layers OAuth 2.0 and OpenID Connect over mutually authenticated transport security. |
| Cloud and SaaS authorization converged on a common vocabulary | Google, Microsoft, GitHub, Salesforce, AWS Cognito, Okta, and many other platforms expose OAuth 2.0 authorization endpoints or grant flows, allowing client libraries and integration products to reuse the same broad model. |
| A large implementation and services market emerged | Microsoft says more than 720,000 organizations use Entra ID, Auth0 reports more than 2,000 enterprise customers and 42 million daily logins, and Okta says two-thirds of the Fortune 100 use its identity products. |
| The original “implicit” and password grants are dying | RFC 9700 says the resource-owner password credentials grant must not be used, while OAuth 2.1 omits both that grant and the implicit grant and makes PKCE the baseline for authorization-code clients. |
| Regulators turned an Internet framework into procurement infrastructure | UK Open Banking’s 2018 governance decision moved its security profile to FAPI, and the standards body has encouraged account-servicing institutions to obtain OpenID Foundation conformance certification. |
| OAuth’s flexibility also preserved vendor variation | The framework admits that its optional components and undefined discovery, registration, and capability mechanisms can yield non-interoperable implementations requiring provider-specific configuration. Aaron Parecki later catalogued those variations and observed that most implementations were not automatically interoperable. |
| Sources for Table: [3] [?] [?] [?] [?] [?] [?] [?] [?] [?] [?] [?] [?] [?] [?] [?] [?] [?] [?] |
Position in the Ecosystem Stack
What it depends on
| Dependency | Role beneath OAuth 2.0 |
| HTTP and HTTP redirection | OAuth’s authorization and token interactions are HTTP-based, and browser redirection carries the resource owner between the client and authorization server. |
| TLS / HTTPS | The authorization endpoint requires TLS, while current security guidance recommends end-to-end modern TLS between clients and resource servers. |
| URI Generic Syntax, RFC 3986 | Redirect endpoints and other protocol locations are represented and validated as URIs. |
| JSON | Token and error responses use JSON structures; RFC 6749 normatively referenced the then-current JSON specification, RFC 4627. |
| HTML form encoding | Authorization and token parameters use application/x-www-form-urlencoded conventions. |
| ABNF, RFC 5234 | RFC 6749 uses ABNF to define protocol-element syntax. |
What depends on it
| Downstream specification or convention | Relationship to OAuth 2.0 |
| OpenID Connect Core 1.0 | Adds authentication and end-user claims on top of OAuth 2.0. |
| Financial-grade API 1.0 and 2.0 | Profiles OAuth for high-value, higher-assurance APIs, including banking and government deployments. |
| User-Managed Access 2.0 | Uses OAuth roles and tokens to coordinate policy-based, asynchronous sharing of protected resources. |
| IndieAuth | Adds URL-based identity semantics to OAuth and is used by Micropub clients to obtain bearer tokens. |
| Solid-OIDC | Combines OAuth, OpenID Connect, DPoP, and WebID-oriented identity for decentralized Solid data pods. |
| AT Protocol OAuth profile | Uses OAuth 2.1 as its base and adds mandatory PKCE, PAR, DPoP, and URL-based client metadata for decentralized social-network clients. |
| Model Context Protocol authorization | Uses OAuth protected-resource metadata, authorization-server discovery, audience binding, and authorization-code patterns for remote tool access. |
| Open-banking security profiles | UK Open Banking and comparable ecosystems use FAPI and OpenID Connect as hardened OAuth-based security layers. |
Companion specs
Lineage
Predecessors
| Predecessor | What it contributed and why the ecosystem moved on |
| Credential sharing and proprietary API tokens | These enabled integrations but gave third parties broad credentials, weak revocation, and vendor-specific behavior; OAuth replaced them with provider-issued, scoped tokens. |
| OAuth Core 1.0 / RFC 5849 | OAuth 1.0 established delegated authorization and request signing, but imposed more client-side cryptographic complexity and had limited extensibility; OAuth 2.0 was a redesign informed by implementation experience and a session-fixation vulnerability. |
| OAuth WRAP | WRAP explored bearer-token and enterprise-friendly profiles; the first OAuth 2.0 draft explicitly combined WRAP with OAuth 1.0a. |
| OpenID 1.x/2.0 | OpenID addressed authentication rather than delegated API access; the original OAuth community emerged because OpenID alone could not authorize a third-party application to use an API. |
| SAML 2.0 and WS- security stacks * | These supplied enterprise federation and assertion patterns but were heavier and less natural for consumer-web APIs; OAuth retained extension points for SAML assertions rather than attempting to replace every enterprise identity workflow. |
Parallel efforts
| Parallel effort | Distinguishing bet and adoption signal |
| SAML 2.0 | Uses signed XML assertions and established trust relationships, remaining common in enterprise workforce federation; OAuth and OpenID Connect instead emphasize HTTP APIs, tokens, and application delegation. |
| AWS Signature Version 4 | Signs each AWS API request with service-, region-, and date-scoped derived credentials rather than using bearer-token delegation as the universal API model. |
| IndieAuth | Retains OAuth’s token machinery but identifies users and clients with URLs, minimizing dependence on a centralized client-registration authority. |
| GNAP | Starts from dynamic negotiation and key-bound requests rather than OAuth’s pre-registered client, grant-type, and bearer-token heritage; RFC 9635 explicitly says it is neither an OAuth extension nor directly compatible with OAuth 2.0. |
Likely successors
| Candidate | Status and succession thesis |
| OAuth 2.1 | The direct, backward-conscious successor: an active IETF OAuth Working Group draft that consolidates RFC 6749, PKCE, native-app and browser guidance, and the security BCP into a safer baseline. Revision 17 was published October 30, 2026. |
| GNAP, RFC 9635 | A clean architectural alternative for dynamic clients, negotiated interactions, and key-bound access; its own RFC expects GNAP and OAuth to coexist rather than predicting immediate replacement. |
| AAuth and agent-authorization drafts | Early proposals attempting to represent autonomous software, delegated missions, and agent-specific authority that conventional OAuth client registration does not model cleanly. |
Governance & Stewardship
Editors, chairs, and sponsoring participants
| Person | Role |
| David Recordon | Initial OAuth 2.0 protocol editor; the final RFC says his text was based on OAuth 1.0 and OAuth WRAP. |
| Eran Hammer-Lahav | Initial public-draft editor at Yahoo! and editor through draft 26; he withdrew before publication. |
| Dick Hardt | Co-author of the initial draft, author/editor of OAuth WRAP, final editor of RFC 6749 at Microsoft, and current co-author of OAuth 2.1. |
| Aaron Parecki | Current OAuth 2.1 co-author, OAuth.net maintainer, and active IETF OAuth participant. |
| Torsten Lodderstedt | OAuth 2.1 co-author and principal contributor to OAuth security guidance; he also helped draft RFC 6749’s security considerations. |
| Blaine Cook and Peter Saint-Andre | Chairs when the IETF OAuth Working Group was created in May 2009. |
| Hannes Tschofenig and Rifaat Shekh-Yusef | Current working-group chairs. |
| Michael B. Jones | Current working-group secretary. |
| Lisa Dusseault, Peter Saint-Andre, and Stephen Farrell | Area directors associated with production of RFC 6749. |
Where decisions get made
oauth@ietf.org mailing list, whose archive is linked from each active draft, and in IETF OAuth Working Group meetings and interims.
[5]
[?] [?] Draft state, adoption, shepherding, IESG review, errata, and milestones are recorded in the IETF Datatracker.
[2]
[15]
Extension registrations also flow through IANA registries and designated review mechanisms created by the RFC family. [?] [?] Pace
Versioning policy
Stewardship transition
Political fault lines
Adoption — by Tier
Incumbents
| Implementation | What it ships and relationship to OAuth 2.0 |
| Microsoft Entra ID | Hosted OAuth 2.0/OIDC platform supporting authorization code with PKCE, client credentials, device code, and Microsoft’s on-behalf-of flow; Microsoft reports more than 720,000 customer organizations. |
| Google Identity OAuth 2.0 | Authorization infrastructure for Google APIs, covering web-server, browser, installed, limited-input-device, and service-account scenarios. |
| Okta and Auth0 | Okta and Auth0 : Commercial OAuth 2.0/OIDC authorization servers spanning workforce and customer identity; Auth0 reports 2,000-plus enterprise customers and 42 million logins per day. |
| Keycloak | Widely deployed open-source identity server with RFC 6749, PAR, DPoP, FAPI, device authorization, and partial token-exchange coverage. |
| Amazon Cognito | AWS-managed user directory and authorization server supporting authorization code, implicit, and client-credentials grants plus custom resource-server scopes. |
| GitHub OAuth and GitHub Apps | GitHub ’s delegated API-access implementation; both OAuth Apps and GitHub Apps use OAuth 2.0, with authorization-code and device grants. |
| Salesforce Connected Apps | OAuth 2.0 access to Salesforce REST resources through connected or external client applications and multiple authorization flows. |
Microsoft Entra ID
Google Identity OAuth 2.0
Keycloak
Challengers
| Implementation | What it ships and relationship to OAuth 2.0 |
| Ory Hydra | Headless, cloud-native OAuth 2.0 and certified OpenID Connect server that delegates login and consent to an external application. |
| Curity Identity Server | Commercial authorization server centered on OAuth 2.0, OIDC, FAPI, token exchange, sender-constrained tokens, and API or AI access control. |
| Ping Identity / PingAM | Enterprise authorization server with code, device, client-credentials and legacy grants plus mTLS, token exchange, UMA, and OpenID Connect. |
| WSO2 Identity Server | Deployable and cloud identity server with OAuth/OIDC authorization, token lifecycle, consent, JWT, and policy features. |
| FusionAuth | Developer-focused CIAM server claiming a full OAuth 2.0 implementation alongside OpenID Connect and SAML. |
| Authlete | Headless OAuth/OIDC protocol engine with unusually broad extension and conformance coverage, including FAPI 1.0/2.0, CIBA, DPoP, and verifiable-credential issuance. |
| Spring Authorization Server | Java framework implementing OAuth 2.1 and OpenID Connect with code, client-credentials, refresh, device, PAR, DPoP, revocation, introspection, and metadata endpoints. |
Ory Hydra
Authlete
Curity Identity Server
Innovators
| Implementation | What it explores |
| AT Protocol OAuth | A decentralized OAuth 2.1 profile with PKCE, PAR, DPoP, and URL-addressed client metadata; Bluesky’s PDS and TypeScript SDK implement the server and client sides. |
| Cloudflare Workers OAuth Provider | Serverless OAuth 2.1 authorization and resource-server components specialized for remote MCP servers and AI agents. |
| Solid-OIDC | Decentralized data-pod authorization combining OAuth, OIDC, Web identifiers, and DPoP-bound tokens. |
| IndieAuth | URL-native identity and bearer-token authorization for independent websites and Micropub clients. |
| node-oidc-provider | Embeddable, OpenID-certified OAuth 2.0 authorization server for Node.js frameworks and custom identity products. |
| OAuth2 Proxy | Reverse-proxy pattern that places OAuth/OIDC authentication in front of applications that were not designed to implement it. |
| JavaScript Solid OIDC | A minimal single-file implementation of the Solid-OIDC flow, deliberately shrinking a complex profile to roughly 700 lines and 4 KB compressed. |
AT Protocol OAuth
Cloudflare Workers OAuth Provider
node-oidc-provider
panva project identity, maintains an embeddable JavaScript authorization-server implementation. [?] Coverage of the spec: It implements RFC 6749, OpenID Connect, and numerous extensions and can be mounted into Connect, Express, Fastify, Hapi, or Koa applications. [?] Adoption signal: The repository had approximately 3,800 GitHub stars in November 2026. [?] Why it matters: It lets product teams build deeply customized authorization services without adopting a full external identity suite, making it a proving ground for emerging OAuth and OIDC features. [?] Notable Holdouts
Critique & Open Disputes
| Critic | Public argument |
| Eran Hammer-Lahav ( archived critique ) | “OAuth 2.0 is a bad protocol”: committee compromises produced something more complex, less interoperable, less complete, and less secure than OAuth 1.0, with safety dependent on expert implementers. |
| Aaron Parecki ( essay ) | RFC 6749 leaves so many security and deployment questions unspecified that most implementations are not automatically interoperable. |
| Daniel Fett, Ralf Küsters, and Guido Schmitz ( formal analysis ) | Their formal model uncovered previously unknown attacks that broke OAuth authorization and authentication guarantees until additional mitigations were applied. |
| Justin Richer ( interview ) | OAuth has become a loose collection of related protocols whose implementers must profile correctly; GNAP adopts a dynamic-first trust model because OAuth assumes stronger prior relationships among participants. |
| Dick Hardt ( agent-authorization interview ) | OAuth was designed around relatively static server relationships and does not naturally handle an autonomous agent encountering a new resource and obtaining task-specific authority on the fly. |
Frontier & Open Questions
| Open question | Likely driver and current status |
| Will OAuth 2.1 finally reach RFC status without reopening compatibility disputes? | Dick Hardt, Aaron Parecki, Torsten Lodderstedt, chairs Hannes Tschofenig and Rifaat Shekh-Yusef, and the OAuth WG control the path; revision 17 was active in October 2026 with an end-of-2026 IESG-submission milestone. |
| How quickly can providers remove implicit and password grants without breaking installed customers? | RFC 9700 and OAuth 2.1 set the policy, but Microsoft and other large platforms still expose legacy modes while recommending migration. |
| Will sender-constrained tokens become the normal case rather than a high-assurance option? | DPoP implementers including Keycloak, Google, FAPI vendors, and the OAuth WG will drive the answer; Keycloak has promoted DPoP to full support and Google now recommends considering it. |
| Can OAuth represent autonomous agents, delegated missions, and human approval across multiple service hops? | Competing individual drafts include AAuth, Agent Authorization Grant, transaction tokens for agents, and an OAuth agent-use-case analysis; IETF 126 devoted explicit agenda time to “Agents Use Cases & Gaps.” |
| How should identity and authorization context propagate across trust domains? | The OAuth Identity and Authorization Chaining draft had reached the RFC Editor queue by mid-2026, while the Transaction Tokens draft remained active and had passed through Working Group Last Call. |
| Can native applications prove that a genuine, untampered client instance is requesting tokens? | draft-ietf-oauth-attestation-based-client-auth-12 had Working Group consensus and was waiting for write-up in October 2026; platform vendors and attestation providers will determine practical adoption. |
| Can first-party applications replace the forbidden password grant without rebuilding every native login journey around browser redirection? | Aaron Parecki and the first-party-apps authors are advancing an active WG draft, but the document itself warns that browser implementation complexity may outweigh the user-experience benefit. |
| Will GNAP remain a specialist parallel protocol or become the clean-slate successor for dynamic systems? | The GNAP community and implementers must prove deployment value; RFC 9635 currently anticipates coexistence and migration mapping rather than rapid replacement. |
Media, Voices, and Coverage
Editor & Maintainer Voices
| Name | Platform | Why follow |
| Aaron Parecki | Personal site | OAuth 2.1 co-author’s running commentary on drafts, PKCE, implementation traps, and IETF work. |
| Dick Hardt | GitHub and talks | Final RFC 6749 editor and OAuth 2.1 co-author, now publicly examining where OAuth fails for autonomous software. |
| OAuth.net | Community reference maintained by active standards participants | Tracks core RFCs, security profiles, events, and active drafts without reducing OAuth to RFC 6749 alone. |
| IETF OAuth mailing list | Public standards archive | The authoritative record for draft disputes, adoption calls, and working-group consensus. |
| IETF OAuth Datatracker | Governance and document tracker | Names chairs, milestones, active documents, meetings, shepherds, and document status. |
Implementer Coverage
| Name | Platform | Why follow |
| Google OAuth Best Practices | Google for Developers | Documents operational token storage, incremental authorization, PKCE, DPoP, revocation, and scope policies at global-provider scale. |
| Microsoft identity platform OAuth documentation | Microsoft Learn | Shows how a major enterprise platform profiles OAuth across browser, native, service, device, and delegated-service scenarios. |
| Keycloak standards coverage | Keycloak project | A useful public matrix of which OAuth-family RFCs are supported, previewed, or partial. |
| Ory Hydra | Ory documentation | Strong coverage of headless authorization-server architecture and separation of login from protocol processing. |
| Authlete | Product and engineering resources | Tracks leading-edge FAPI, CIBA, DPoP, and verifiable-credential conformance earlier than many full-suite vendors. |
| Cloudflare MCP Authorization | Cloudflare Developers | Documents the practical collision between OAuth, MCP discovery, remote tools, and serverless agent infrastructure. |
Critic Coverage
| Name | Platform | Why follow |
| Eran Hammer-Lahav, “OAuth 2.0 and the Road to Hell” | Archived essay | The canonical insider critique of extensibility, bearer security, committee governance, and interoperability. |
| Daniel Fett, Ralf Küsters, and Guido Schmitz | Academic security research | Formalized OAuth’s security properties, discovered new attacks, and proved a mitigated model. |
| Justin Richer | Center for Internet Security interview | Explains why OAuth’s collection of profiles and prior-trust assumptions motivated GNAP’s dynamic-first design. |
| Aaron Parecki, “So You Implemented an OAuth 2.0 API” | Personal essay | Catalogues the decisions RFC 6749 leaves open and therefore the real sources of cross-provider incompatibility. |
Conferences & Working Group Forums
| Forum | Platform | Why follow |
| OAuth Security Workshop | Annual specialist workshop | The principal venue connecting academic researchers, IETF participants, implementers, and identity-security practitioners. |
| IETF OAuth meetings | Public meetings, minutes, slides, and recordings | The formal venue for working-group draft advancement and live issue resolution. |
| Identiverse — State of OAuth | Conference talk | Aaron Parecki’s maintainer-level overview of OAuth 2.1 and the expanding companion-spec stack. |
| Changelog: “OAuth, It’s Complicated” | Podcast | A candid discussion with Parecki about PKCE, OAuth 2.1, GNAP, and why “OAuth 2” denotes a family rather than one interoperable protocol. |
| Identity, Unlocked — OAuth 2.1 | Podcast and transcript | Vittorio Bertocci and Aaron Parecki explain the consolidation thesis and mandatory-PKCE direction behind OAuth 2.1. |
Adjacent Specs and Standards
| Spec | How it adjoins OAuth 2.0 |
| OAuth 1.0 / RFC 5849 | Direct predecessor, retaining per-request signatures and a less extensible architecture. |
| OAuth 2.1 | Intended consolidation of OAuth 2.0 with current PKCE, native-app, browser-app, and security best practices. |
| OAuth 2.0 Bearer Token Usage / RFC 6750 | Defines the dominant access-token presentation method used with RFC 6749. |
| Proof Key for Code Exchange / RFC 7636 | Protects authorization codes from interception and is becoming mandatory across client classes. |
| OAuth 2.0 Security Best Current Practice / RFC 9700 | Updates the framework for known attacks and deprecates unsafe modes. |
| OpenID Connect Core 1.0 | Adds authentication and identity claims above OAuth’s authorization layer. |
| OAuth 2.0 Pushed Authorization Requests / RFC 9126 | Moves authorization-request payloads to a protected back channel before browser redirection. |
| OAuth 2.0 DPoP / RFC 9449 | Binds tokens to a client-held key to reduce bearer-token replay. |
| OAuth 2.0 Authorization Server Metadata / RFC 8414 | Standardizes endpoint and capability discovery. |
| Financial-grade API 2.0 | High-assurance profile for valuable and regulated API transactions. |
| Grant Negotiation and Authorization Protocol / RFC 9635 | Clean-slate, non-compatible parallel protocol for dynamic and negotiated authorization. |
| Model Context Protocol Authorization | Applies the OAuth family to remote AI-agent tools and protected resources. |
Sources
[1] datatracker.ietf.org . OAuth Identity and Authorization Chaining Across Domains . Updated: 2026, Nov 06. Generated: 2026, Nov 06. Perplexity API response.
[2] datatracker.ietf.org . RFC 6569: Guidelines for Development of an Audio Codec within ... . Updated: 2026, Nov 06. Generated: 2026, Nov 06. Perplexity API response.
[3] datatracker.ietf.org . OAuth . Updated: 2026, Nov 06. Generated: 2026, Nov 06. Perplexity API response.
[4] datatracker.ietf.org . Document Search - IETF Datatracker . Updated: 2026, Oct 27. Generated: 2026, Nov 06. Perplexity API response.
[5] datatracker.ietf.org . RFC 8179 - Intellectual Property Rights in IETF Technology . Updated: 2026, Nov 06. Generated: 2026, Nov 06. Perplexity API response.
[6] datatracker.ietf.org . Web Authorization Protocol (oauth) - datatracker.ietf.org . Updated: 2026, Nov 06. Generated: 2026, Nov 06. Perplexity API response.
[7] datatracker.ietf.org . draft-ietf-oauth-v2-00 . Updated: 2026, Oct 31. Generated: 2026, Nov 06. Perplexity API response.
[8] datatracker.ietf.org . The OAuth 2.1 Authorization Framework . Updated: 2026, Nov 06. Generated: 2026, Nov 06. Perplexity API response.
[9] trustee.ietf.org . Corrected Legal Provisions Relating to IETF Documents . Updated: 2026, Oct 26. Generated: 2026, Nov 06. Perplexity API response.
[10] datatracker.ietf.org . Intellectual Property Rights in IETF Technology . Updated: 2026, Oct 25. Generated: 2026, Nov 06. Perplexity API response.
[11] 2016, Jan 07. rfc-editor.org . Best Current Practice for OAuth 2.0 Security . Updated: 2026, Oct 19. Generated: 2026, Nov 06. Perplexity API response.
[12] datatracker.ietf.org . The OAuth 2.0 Authorization Framework . Updated: 2026, Nov 06. Generated: 2026, Nov 06. Perplexity API response.
[13] 2012, Oct 01. dl.acm.org . RFC 6749: The OAuth 2.0 Authorization Framework . Updated: 2026, Nov 02. Generated: 2026, Nov 06. Perplexity API response.
[14] datatracker.ietf.org . datatracker.ietf.org · doc · rfc9101RFC 9101 - The OAuth 2.0 Authorization Framework: JWT-Secured ... . Updated: 2026, Nov 06. Generated: 2026, Nov 06. Perplexity API response.
[15] trustee.ietf.org . Copyright - IETF Trust . Updated: 2026, Oct 07. Generated: 2026, Nov 06. Perplexity API response.
[16] datatracker.ietf.org . https://datatracker.ietf.org/doc/draft-hammer-oaut... . Updated: 2026, May 23. Generated: 2026, Nov 06. Perplexity API response.
[17] 2010, Mar 09. github.com . OAuth-2.0/draft-recordon-oauth-v2-upgrade.xml at master · davidrecordon/OAuth-2.0 . Updated: 2026, Oct 25. Generated: 2026, Nov 06. Perplexity API response.
[18] trustee.ietf.org . [PDF] IETF Trust Legal Provisions Relating to IETF Documents Effective ... . Updated: 2026, Jul 19. Generated: 2026, Nov 06. Perplexity API response.
[19] datatracker.ietf.org . RFC 6749 - The OAuth 2.0 Authorization Framework . Updated: 2026, Oct 31. Generated: 2026, Nov 06. Perplexity API response.
[20] rfc-editor.org . rfc6749 . Updated: 2026, Oct 27. Generated: 2026, Nov 06. Perplexity API response.
[21] rfc-editor.org . » RFC Editor . Updated: 2026, Sep 24. Generated: 2026, Nov 06. Perplexity API response.
[22] 2026, May 20. datatracker.ietf.org . The OAuth 2.0 Authorization Framework . Updated: 2026, Nov 06. Generated: 2026, Nov 06. Perplexity API response.
[23] datatracker.ietf.org . Web Authorization Protocol (oauth) . Updated: 2026, Nov 06. Generated: 2026, Nov 06. Perplexity API response.
[24] 2020, Feb 11. oauth.com . Background - OAuth 2.0 Simplified . Updated: 2026, Oct 06. Generated: 2026, Nov 06. Perplexity API response.
[25] datatracker.ietf.org . OAuth 2.0 Security Best Current Practice . Updated: 2026, Nov 06. Generated: 2026, Nov 06. Perplexity API response.
[26] 2026, Apr 30. ietf.org . A Comprehensive Roadmap for OAuth 2.0 Standards and ... . Updated: 2026, Oct 04. Generated: 2026, Nov 06. Perplexity API response.
[27] irurueta.com . How OAuth Evolved - Irurueta Docs . Updated: 2026, Oct 31. Generated: 2026, Nov 06. Perplexity API response.
[28] datatracker.ietf.org . Updates to OAuth 2.0 Security Best Current Practice . Updated: 2026, Nov 06. Generated: 2026, Nov 06. Perplexity API response.
[29] 2026, May 20. datatracker.ietf.org . OAuth 2.0 for Native Apps - Internet Engineering Task Force . Updated: 2026, Nov 06. Generated: 2026, Nov 06. Perplexity API response.
[30] datatracker.ietf.org . Active Internet-Drafts - IETF Datatracker . Updated: 2026, Nov 07. Generated: 2026, Nov 06. Perplexity API response.
[31] datatracker.ietf.org . The OAuth 2.1 Authorization Framework . Updated: 2026, Nov 06. Generated: 2026, Nov 06. Perplexity API response.
[32] datatracker.ietf.org . draft-chen-oauth-roadmap-01 - A Comprehensive ... . Updated: 2026, Nov 06. Generated: 2026, Nov 06. Perplexity API response.
[33] datatracker.ietf.org . Web Authorization Protocol (oauth) . Updated: 2026, Oct 31. Generated: 2026, Nov 06. Perplexity API response.
[34] 2026, Apr 30. datatracker.ietf.org . draft-chen-oauth-roadmap-00 - IETF Datatracker . Updated: 2026, Oct 30. Generated: 2026, Nov 06. Perplexity API response.
[35] 2026, Oct 30. datatracker.ietf.org . History for draft-ietf-oauth-v2-1 -17 . Updated: 2026, Nov 07. Generated: 2026, Nov 06. Perplexity API response.
[36] 2026, Nov 01. ietf.org . AAuth - Agentic Authorization OAuth 2.1 Extension . Generated: 2026, Nov 06. Perplexity API response.
[37] datatracker.ietf.org . Writeups for charter-ietf-oauth-06 . Updated: 2026, Nov 03. Generated: 2026, Nov 06. Perplexity API response.
[38] datatracker.ietf.org . Web Authorization Protocol (oauth) - IETF Datatracker . Updated: 2026, Oct 31. Generated: 2026, Nov 06. Perplexity API response.
[39] ietf.org . Intellectual property rights (IPR) . Updated: 2026, Oct 02. Generated: 2026, Nov 06. Perplexity API response.
[40] ietf.org . Guidelines to Authors of Internet-Drafts . Updated: 2026, Oct 31. Generated: 2026, Nov 06. Perplexity API response.
[41] datatracker.ietf.org . RFC 5378 - Rights Contributors Provide to the IETF Trust . Updated: 2026, Nov 06. Generated: 2026, Nov 06. Perplexity API response.
[42] trustee.ietf.org . The IETF Trust's Copyrights and Licenses . Updated: 2026, Oct 13. Generated: 2026, Nov 06. Perplexity API response.
[43] datatracker.ietf.org . RFC 3979 - Intellectual Property Rights in IETF Technology . Updated: 2026, Oct 31. Generated: 2026, Nov 06. Perplexity API response.
[44] trustee.ietf.org . Licenses – IETF Trust - Internet Engineering Task Force . Updated: 2026, Oct 21. Generated: 2026, Nov 06. Perplexity API response.
[45] datatracker.ietf.org . RFC 3978 - IETF Rights in Contributions - IETF Datatracker . Updated: 2026, Oct 30. Generated: 2026, Nov 06. Perplexity API response.
[46] datatracker.ietf.org . The OAuth 2.0 Protocol draft-hammer-oauth2-00 - IETF Datatracker . Updated: 2026, Sep 16. Generated: 2026, Nov 06. Perplexity API response.
[47] datatracker.ietf.org . draft-recordon-oauth-v2-device-00 . Updated: 2026, Oct 30. Generated: 2026, Nov 06. Perplexity API response.
[48] datatracker.ietf.org . draft-ietf-oauth-v2-bearer-00 . Updated: 2026, Nov 01. Generated: 2026, Nov 06. Perplexity API response.
[49] datatracker.ietf.org . The OAuth 2.0 Protocol draft-hammer-oauth2-00 . Updated: 2026, Nov 01. Generated: 2026, Nov 06. Perplexity API response.
[50] 2010, Mar 09. github.com . GitHub - davidrecordon/OAuth-2.0: DRAFT . Updated: 2026, Oct 24. Generated: 2026, Nov 06. Perplexity API response.