Browse Prior Art Database

OAuth 2.0 Dynamic Client Registration Protocol (RFC7591)

IP.com Disclosure Number: IPCOM000242386D
Original Publication Date: 2015-Jul-01
Included in the Prior Art Database: 2015-Jul-10
Document File: 78 page(s) / 88K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Richer: AUTHOR [+6]

Abstract

In order for an OAuth 2.0 [RFC6749] client to utilize an OAuth 2.0 authorization server, the client needs specific information to interact with the server, including an OAuth 2.0 client identifier to use at that server. This specification describes how an OAuth 2.0 client can be dynamically registered with an authorization server to obtain this information.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 3% of the total text.

Internet Engineering Task Force (IETF)                    J. Richer, Ed. Request for Comments: 7591 Category: Standards Track                                       M. Jones ISSN: 2070-1721                                                Microsoft                                                               J. Bradley                                                            Ping Identity                                                              M. Machulak                                                     Newcastle University                                                                  P. Hunt                                                       Oracle Corporation                                                                July 2015

              OAuth 2.0 Dynamic Client Registration Protocol

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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7591.

 Richer, et al.               Standards Track                    [Page 1]
 RFC 7591             OAuth 2.0 Dynamic Registration            July 2015

 Copyright Notice

   Copyright (c) 2015 IETF Trust and the persons identified as the    document authors.  All rights reserved.

  ...