References to RFC 7636
These dependencies are extracted using heuristics looking for strings with particular prefixes. Notably, this means that references to I-Ds by title only are not reflected here. If it's really important, please inspect the documents' references sections directly.
Showing RFCs and active Internet-Drafts, sorted by reference type, then document name.
Document | Title | Status | Type | Downref |
---|---|---|---|---|
draft-ietf-oauth-browser-based-apps |
OAuth 2.0 for Browser-Based Apps
References Referenced by |
normatively references | ||
draft-parecki-oauth-first-party-apps |
OAuth 2.0 for First-Party Applications
References Referenced by |
normatively references | ||
RFC 8414 |
OAuth 2.0 Authorization Server Metadata
References Referenced by |
Proposed Standard | normatively references | |
draft-ietf-oauth-security-topics |
OAuth 2.0 Security Best Current Practice
References Referenced by |
Best Current Practice | informatively references | |
draft-ietf-oauth-v2-1 |
The OAuth 2.1 Authorization Framework
References Referenced by |
informatively references | ||
RFC 8252 |
OAuth 2.0 for Native Apps
References Referenced by |
Best Current Practice | informatively references | |
RFC 9126 |
OAuth 2.0 Pushed Authorization Requests
References Referenced by |
Proposed Standard | informatively references | |
RFC 9449 |
OAuth 2.0 Demonstrating Proof of Possession (DPoP)
References Referenced by |
Proposed Standard | informatively references |