OAuth 2.0 Dynamic Client Registration Protocol
RFC 7591, “OAuth 2.0 Dynamic Client Registration Protocol”, is a Proposed Standard document published in July 2015 by J. Richer, M. Jones, J. Bradley, M. Machulak, P. Hunt. The canonical text is published by the RFC Editor.
Abstract
This specification defines mechanisms for dynamically registering OAuth 2.0 clients with authorization servers. Registration requests send a set of desired client metadata values to the authorization server. The resulting registration responses return a client identifier to use at the authorization server and the client metadata values registered for the client. The client can then use this registration information to communicate with the authorization server using the OAuth 2.0 protocol. This specification also defines a set of common client metadata fields and values for clients to use during registration.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 7591 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7590 Use of Transport Layer Security in the Extensible Messaging and Presence Protocol
- RFC 7592 OAuth 2.0 Dynamic Client Registration Management Protocol
- RFC 7589 Using the NETCONF Protocol over Transport Layer Security with Mutual X.509 Authentication
- RFC 7593 The eduroam Architecture for Network Roaming
- RFC 7588 A Widely Deployed Solution to the Generic Routing Encapsulation Fragmentation Problem
- RFC 7594 A Framework for Large-Scale Measurement of Broadband Performance
- RFC 7587 RTP Payload Format for the Opus Speech and Audio Codec
- RFC 7595 Guidelines and Registration Procedures for URI Schemes