registration_
Registry Context
The authorization server provides this URL to identify the client configuration endpoint for a specific client. The client must use the URL as supplied and must not construct it independently.
Technical Summary
A Client Information Response member defined by RFC 7592 containing the fully qualified URL of the client configuration endpoint for a specific client.
When Used
In Client Information Responses supporting subsequent viewing, updating, or deletion of a dynamically registered client's configuration.
Normative Requirements
Clients
RFC 7592 - Section Appendix B
construct the client configuration endpoint URL from component pieces..
MUST NOT construct this URL from component pieces
RFC 7592 - Section Appendix B
use the client configuration endpoint URL as given by the authorization server..
Condition: after receiving registration_client_uri
The client MUST use the URL as given by the server
Authorization servers
RFC 7592 - Section Appendix B
expect the client to construct or discover the client configuration endpoint URL independently..
MUST NOT expect the client to construct or discover this URL on its own
RFC 7592 - Section Appendix B
provide the client with the fully qualified URL in the registration_client_uri element..
Condition: in the Client Information Response
MUST provide the client with the fully qualified URL in the "registration_client_uri" element
RFC 7592 - Section Appendix B
match the client to which the request pertains against the client to which the registration access token was issued..
Condition: when the endpoint URL identifies the client associated with a request
MUST be matched against the client to which the registration access token was issued
RFC 7592 - Section 3
include registration_client_uri as a string containing the fully qualified URL of the client configuration endpoint for this client..
Condition: in the Client Information Response
REQUIRED. String containing the fully qualified URL of the client configuration endpoint for this client.
RFC 7592 - Section Appendix B
form the endpoint URL using a server-constructed string combining the client registration endpoint URL and the issued client_id, with the client_id as a path or query parameter..
It is RECOMMENDED that this endpoint URL be formed through the use of a server-constructed URL string
RFC 7592 - Section Appendix B
return the client registration endpoint URL as the client configuration endpoint URL and vary behavior according to the registration access token's authentication context..
Condition: if desired
the server MAY simply return the client registration endpoint URL as the client configuration endpoint URL
Validation Guidance
Verify that registration_client_uri is present in the Client Information Response, is a string, and contains a fully qualified URL.
Treat registration_client_uri as an opaque server-provided URL; do not derive, reconstruct, or independently discover it.
When processing a management request, verify that the client concerned matches the client associated with the registration access token.
A server-constructed URL combining the registration endpoint and client_id is recommended, but other URL forms are permitted.
Security Notes
RFC 7592 - Section Appendix B
The client identified for a management request must match the client to which the registration access token was issued.
Reference
Details
- Entry Id
registration_client_ uri - Client Metadata Name
registration_client_ uri - Client Metadata Description
Fully qualified URI of the client registration endpoint- Change Controller
IESG- Reference
RFC7592