Dynamic client configuration updating policy information
If desired, representation of this Claim in different languages and scripts is represented as described in Section 2.1 OPTIONAL.
If present, the server SHOULD display this URL to the End-User in a followable fashion.
The service can be added to an existing A record or it can be added when the A record is created.
See Quick Task: Create Dynamic DNS Host for instructions on setting up the Dynamic DNS Service.
The means by which the Authorization Server issues this token and the means by which the Registration Endpoint validates it are also out of scope.
The contents of this token are service-specific and are out of scope for this specification.
OAuth 2.0 Bearer Token issued by the Authorization Server through the Client Registration Endpoint that is used to authenticate the caller when accessing the Client's registration information at the Client Configuration Endpoint.
This URL for this endpoint is returned by the Authorization Server in the Client Information Response.
When deleting a Dynamic Update User currently used by an Update Client, make sure to replace the deleted user with a new Dynamic Update User in the Update Client.
The following information may be helpful in selecting and configuring an appropriate update client for you needs: Hardware and Software Update Clients A list of currently supported software update clients is available on the Dyn DNS site: Update Client Specification If you are interested in writing your own update client, the API specification is available on the Dyn DNS site: Please note: Currently certified update clients only support dynamic updates to IPv4 host records.
For details on dynamic updates to IPv6 host records, please contact your Dyn Concierge.
Open ID Connect 1.0 is a simple identity layer on top of the OAuth 2.0 protocol. The value of this field MUST point to a valid web page.
It enables Clients to verify the identity of the End-User based on the authentication performed by an Authorization Server, as well as to obtain basic profile information about the End-User in an interoperable and REST-like manner. The Open ID Provider SHOULD display this URL to the End-User if it is given.
Clients have metadata associated with their unique Client Identifier at the Authorization Server.