Get OAuth2 Client using OpenID Dynamic Client Registration
This endpoint behaves like the administrative counterpart (`getOAuth2Client`) but is capable of facing the
GET /oauth2/register/{id}
This endpoint behaves like the administrative counterpart (getOAuth2Client) but is capable of facing the
public internet directly and can be used in self-service. It implements the OpenID Connect
Dynamic Client Registration Protocol.
To use this endpoint, you will need to present the client's authentication credentials. If the OAuth2 Client
uses the Token Endpoint Authentication Method client_secret_post, you need to present the client secret in the URL query.
If it uses client_secret_basic, present the Client ID and the Client Secret in the Authorization header.
Operation ID: getOidcDynamicClient Tag: oidc
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
id | string | yes | The id of the OAuth 2.0 Client. |
Responses
| Status | Description | Body |
|---|---|---|
| 200 | oAuth2Client | application/json, object |
| default | Default Error Response | application/json, object |
Security
bearer
Generated from ../athena/openapi.json at build time.
Register OAuth2 Client using OpenID Dynamic Client Registration
This endpoint behaves like the administrative counterpart (`createOAuth2Client`) but is capable of facing the
Set OAuth2 Client using OpenID Dynamic Client Registration
This endpoint behaves like the administrative counterpart (`setOAuth2Client`) but is capable of facing the