-
Notifications
You must be signed in to change notification settings - Fork 3
Service: OAuth2 Client Deregistration
Eliza Margaretha edited this page May 20, 2022
·
12 revisions
removes an OAuth2 Client from the registry. All access tokens, refresh tokens and authorization codes associated with the client will be revoked. Deregistration requires client-owner authentication. This service is not part of the official OAuth2 specification.
Available in: full version
Method: DELETE
Service URL: root/oauth2/client/deregister/{client_id}
Header Parameters
Name | Required | Description | Value |
---|---|---|---|
Authorization | yes | HTTP authentication with scheme: Bearer | OAuth2 access token |
Path Parameter
Name | Required | Description | Type |
---|---|---|---|
client_id | yes | the client id | String |
Deregistering a public client
curl --request delete -H 'Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=' http://localhost:8089/api/oauth2/client/deregister/fCBbQkAxMDEyMmQwOQ==
Parecki, Aaron. OAuth 2.0 Servers. [Online]. Available: https://www.oauth.com/
- Importing Kustvakt to Eclipse
- Installing Lombok
- Setting annotation processors
- Setting test environment
- HTTP Basic Authentication
- OAuth2 authorization scopes
- OAuth2 authorization request
- OAuth2 token request
- OAuth2 token revocation
- OAuth2 client registration
- OAuth2 client info
- OAuth2 client deregistration
- OAuth2 client secret reset
- Plugin registration
- Plugin list (marketplace)
- Plugin installation
- Plugin uninstallation
- Installed plugin list
- VC creation and update
- VC deletion
- VC list
- VC info
- VC KoralQuery
- VC statistics
- VC statistics with KoralQuery