RFC 7591: OAuth 2.0 Dynamic Client Registration Protocol

This specification defines mechanisms for dynamically registering OAuth 2.0 clients with authorization servers. Registration requests send a set of desired…

Read RFC 7591 on the RFC Editor

Outgoing relationships (12 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 5226: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 5246: The Transport Layer Security (TLS) Protocol Version 1.2
Normative reference — RFC 6125: Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)
Normative reference — RFC 5646: Tags for Identifying Languages
Normative reference — RFC 7519: JSON Web Token (JWT)
Normative reference — RFC 6749: The OAuth 2.0 Authorization Framework
Normative reference — RFC 7159: The JavaScript Object Notation (JSON) Data Interchange Format
Normative reference — RFC 7515: JSON Web Signature (JWS)
Normative reference — RFC 7517: JSON Web Key (JWK)
Normative reference — RFC 7523: JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants
Normative reference — RFC 7522: Security Assertion Markup Language (SAML) 2.0 Profile for OAuth 2.0 Client Authentication and Authorization Grants

Incoming relationships (11 related RFCs)

Normatively referenced by — RFC 8705: OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access Tokens
Normatively referenced by — RFC 7628: A Set of Simple Authentication and Security Layer (SASL) Mechanisms for OAuth
Normatively referenced by — RFC 7592: OAuth 2.0 Dynamic Client Registration Management Protocol
Normatively referenced by — RFC 9701: JSON Web Token (JWT) Response for OAuth Token Introspection
Normatively referenced by — RFC 9728: OAuth 2.0 Protected Resource Metadata
Informatively referenced by — RFC 9200: Authentication and Authorization for Constrained Environments Using the OAuth 2.0 Framework (ACE-OAuth)
Informatively referenced by — RFC 8252: OAuth 2.0 for Native Apps
Informatively referenced by — RFC 9126: OAuth 2.0 Pushed Authorization Requests
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