OAuth 2.0 Pushed Authorization Requests
Pushed authorization request (PAR) allows clients to push the payload of an OAuth 2.0 authorization request to the authorization server via a direct request.
- from
- OpenID Connect
- added
- 2026-10-10
- likes
- 0
similar
-
OAuth 2.0 Rich Authorization Requests (RAR) datatracker.ietf.org
Extends OAuth 2.0 authorization requests with additional authorization_details parameter that allows clients to specify their fine-grained authorization requirements using the expressiveness of JSON data structures.
-
authorization_code datatracker.ietf.org
OAuth 2.0 Authorization Code Grant Type which fit well public client authorization like web apps.
-
OAuth 2.0 Authorization Framework: Bearer Token Usage datatracker.ietf.org
Describes how to use bearer tokens in HTTP requests to access OAuth 2.0 protected resources.
-
OAuth 2.0 Dynamic Client Registration Protocol datatracker.ietf.org
Defines how an OAuth 2.0 Relying Party (RP) can dynamically register with the OAuth 2.0 server provider.
-
OAuth 2.0 JWT-Secured Authorization Request (JAR) datatracker.ietf.org
Allows to send request parameters in a JSON Web Token (JWT), which can be signed with JSON Web Signature (JWS) and encrypted with JSON Web Encryption (JWE) so that the integrity, source authentication, and confidentiality properties of the authorization request are attained.
-
OAuth 2.0 for First-Party Applications datatracker.ietf.org
Defines the Authorization Challenge Endpoint to enable native applications to obtain user authorization through native user interfaces.
OpenID Connect › Resources > Specifications > Published: “Pushed authorization request (PAR) allows clients to push the payload of an OAuth 2.0 authorization request to the authorization server via a direct request.”