Updating client information

In particular, the following individuals have been instrumental in their review and contribution to various draft versions of this document: Amanda Anganes, Derek Atkins, Tim Bray, Domenico Catalano, Donald Coffin, Vladimir Dzhuvinov, George Fletcher, Thomas Hardjono, Phil Hunt, William Kim, Torsten Lodderstedt, Eve Maler, Josh Mandel, Nov Matake, Tony Nadalin, Nat Sakimura, Christian Scholz, and Hannes Tschofenig.

The authorization server MUST provide the client with the fully qualified URL in the "registration_client_uri" element of the Client Information Response, as specified in Section 3.

Status of This Memo This document is not an Internet Standards Track specification; it is published for examination, experimental implementation, and evaluation.

Request for Comments: 7592 Category: Experimental M. Not all authorization servers supporting dynamic client registration will support these management methods.

This document is a product of the Internet Engineering Task Force (IETF). It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG).

Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.

Search for updating client information:

updating client information-50updating client information-88updating client information-18updating client information-26

If a registration access token is shared between client instances, one instance could change or delete registration values for all other instances of the client.

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “updating client information”