metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 7591: OAuth 2.0 Dynamic Client Registration Protocol

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC7591
Published
July 2015
Authors
J. Richer; M. Jones; J. Bradley; M. Machulak; P. Hunt
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
39
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/7591-oauth-2-0-dynamic-client-registration-protocol