Client Registration Request Using a Software Relationship between Grant Types and Response Types. The Trust Legal Provisions and are provided without warranty asġ. Include Simplified BSD License text as described in Section 4.e of Code Components extracted from this document must Please review these documentsĬarefully, as they describe your rights and restrictions with respect This document is subject to BCP 78 and the IETF Trust's Legal RFC 7591 OAuth 2.0 Dynamic Registration July 2015Ĭopyright (c) 2015 IETF Trust and the persons identified as the Make the cut 3.2.1 registration code how to#Information about the current status of this document, any errata,Īnd how to provide feedback on it may be obtained at Internet Standards is available in Section 2 of RFC 5741. Internet Engineering Steering Group (IESG). Received public review and has been approved for publication by the It represents the consensus of the IETF community. This document is a product of the Internet Engineering Task Force This is an Internet Standards Track document. Of common client metadata fields and values for clients to use during Registration information to communicate with the authorization server Identifier to use at the authorization server and the client metadata The resulting registration responses return a client Send a set of desired client metadata values to the authorization OAuth 2.0 clients with authorization servers. This specification defines mechanisms for dynamically registering OAuth 2.0 Dynamic Client Registration Protocol Internet Engineering Task Force (IETF) J.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |