RFC 9396: OAuth 2.0 Rich Authorization Requests

This document specifies a new parameter authorization_details that is used to carry fine-grained authorization data in OAuth messages.

Read RFC 9396 on the RFC Editor

Outgoing relationships (13 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 7519: JSON Web Token (JWT)
Normative reference — RFC 8414: OAuth 2.0 Authorization Server Metadata
Normative reference — RFC 7662: OAuth 2.0 Token Introspection
Normative reference — RFC 8707: Resource Indicators for OAuth 2.0
Normative reference — RFC 8628: OAuth 2.0 Device Authorization Grant
Informative reference — RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format
Informative reference — RFC 20: ASCII format for network interchange
Informative reference — RFC 6749: The OAuth 2.0 Authorization Framework
Informative reference — RFC 7591: OAuth 2.0 Dynamic Client Registration Protocol
Informative reference — RFC 9101: The OAuth 2.0 Authorization Framework: JWT-Secured Authorization Request (JAR)
Informative reference — RFC 9126: OAuth 2.0 Pushed Authorization Requests

Incoming relationships (2 related RFCs)

Normatively referenced by — RFC 9728: OAuth 2.0 Protected Resource Metadata
Informatively referenced by — RFC 9700: Best Current Practice for OAuth 2.0 Security