RFC 9126: OAuth 2.0 Pushed Authorization Requests

This document defines the pushed authorization request (PAR) endpoint, which allows clients to push the payload of an OAuth 2.0 authorization request to the…

Read RFC 9126 on the RFC Editor

Outgoing relationships (15 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 8174: Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words
Normative reference — RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format
Normative reference — RFC 6749: The OAuth 2.0 Authorization Framework
Normative reference — RFC 8414: OAuth 2.0 Authorization Server Metadata
Normative reference — RFC 9101: The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request (JAR)
Informative reference — RFC 7519: JSON Web Token (JWT)
Informative reference — RFC 7517: JSON Web Key (JWK)
Informative reference — RFC 7591: OAuth 2.0 Dynamic Client Registration Protocol
Informative reference — RFC 6755: An IETF URN Sub-Namespace for OAuth
Informative reference — RFC 7523: JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants
Informative reference — RFC 8705: OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access Tokens
Informative reference — RFC 8707: Resource Indicators for OAuth 2.0
Informative reference — RFC 7636: Proof Key for Code Exchange by OAuth Public Clients
Informative reference — RFC 8252: OAuth 2.0 for Native Apps

Incoming relationships (3 related RFCs)

Informatively referenced by — RFC 9396: OAuth 2.0 Rich Authorization Requests
Informatively referenced by — RFC 9449: OAuth 2.0 Demonstrating Proof of Possession (DPoP)
Informatively referenced by — RFC 9700: Best Current Practice for OAuth 2.0 Security