oauth.net
Dynamic Client Registration Management
RFC 7592 extends Dynamic Client Registration (RFC 7591) with a client configuration endpoint — letting clients read, update, and delete their own registration using a registration access token.
When to use this
Use Dynamic Client Management alongside Dynamic Client Registration in deployments where clients need to update their own metadata over time — for example, to rotate redirect URIs, update a logo, or change the token endpoint authentication method. The authorization server issues a
registration_access_token at registration time that the client uses to authenticate subsequent management requests.
After initial registration, the client receives a registration_client_uri and a registration_access_token. The client can then GET the current registration, PUT an updated registration, or DELETE the registration entirely — all authenticated with the registration access token as a Bearer token.
Related specs
- Dynamic Client Registration RFC 7591 — required prerequisite