Endpoint that lets OAuth 2.0/OpenID Connect clients register dynamically as per RFC7591 and OpenID Connect Dynamic Client Registration 1.0 incorporating errata set 1. The endpoint also lets clients read and update their metadata, as well as deprovision themselves as per RFC7592.
You must compose the path to the register endpoint,
addressing the specific realm where the client is or should be registered/deprovisioned.
By default, AM requires clients to present an access token to register themselves. This behavior is controlled by the Allow Open Dynamic Client Registration switch, under the Dynamic Registration tab of the OAuth 2.0 provider.
Read, update, and delete operations require an authorization bearer header
that includes the
registration_access_token, provided to the client during registration.
The endpoint supports the following methods:
POST. Register clients
GET. Read client information
PUT. Update client information
DELETE. Deprovision a client
For usage information and examples, see Dynamic client registration.