oauth.net
Dynamic Client Registration
Dynamic Client Registration lets OAuth clients register themselves programmatically — submitting their metadata and receiving a client_id (and optionally a client_secret) without any manual setup by the authorization server operator.
When to use this
Use Dynamic Client Registration when clients need to register at runtime — for example, in open ecosystems where any developer can build a client against your API, in federated identity deployments where clients are registered automatically during federation, or in multi-tenant platforms where each tenant gets its own client credentials. Not all authorization servers support or allow open dynamic registration; many require an initial access token to authorize the registration request.
The client POSTs its metadata (redirect URIs, application name, logo URL, token endpoint auth method, etc.) to the registration endpoint and receives a client registration response including a client_id, and for confidential clients a client_secret. This spec was derived from the OpenID Connect Dynamic Client Registration spec and is compatible with OpenID Connect servers.
Related specs
- Dynamic Client Management RFC 7592 — updating registered clients
- Authorization Server Metadata RFC 8414 — discovering the registration endpoint