OAuth 2.0 JWT-Secured Authorization Request (JAR)
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.
- from
- OpenID Connect
- added
- 2026-10-10
- likes
- 0
similar
-
JWT Secured Authorization Response Mode for OAuth 2.0 (JARM) openid.net
JWT-based mode to encode OAuth authorization response parameters with additional claims used to further protect the transmission.
-
JSON Web Signature (JWS) datatracker.ietf.org
Specifications for JWS which represents content secured with digital signatures.
-
JSON Web Encryption (JWE) datatracker.ietf.org
Specifications for JWE which represents encrypted content using JSON-based data structures.
-
JSON Web Token (JWT) datatracker.ietf.org
JWT specifications used for different tokens mentioned in OAuth 2.0 and OpenID Connect specifications.
-
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.
-
JWT, JWS and JWE for Not So Dummies! web.archive.org
A signed JWT is known as a JWS (JSON Web Signature). In fact a JWT does not exist itself — either it has to be a JWS or a JWE (JSON Web Encryption). Its like an abstract class — the JWS and JWE are the concrete implementations.
OpenID Connect › Resources > Specifications > Published: “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.”