revokeUserClient
revokeUserClient(clientId)
DELETE /api/2.0/oauth2/clients/{clientId}/revoke
Revoke client consent
Revokes the calling user's own consent for one client and answers 200 with an empty body. It touches only the caller's grant: other users keep their consents and the client itself stays registered. Guests may call it as well as users and administrators, because it can never reach anyone else's data. The revocation is carried out by the authorization service over gRPC, so a service that reports nothing was revoked produces 400 and a service that cannot be reached produces 503. Once it succeeds the user has to authorize the client again before it can act on their behalf.
Parameters
| Name | In | Type | Description | Notes |
|---|---|---|---|---|
| clientId | path | String | ID of the client to revoke consent for | [required] [example: 6c7cf17b-1bd3-47d5-94c6-be2d3570e168] [minLength: 1] |
Responses
| Status code | Description | Type | Response headers |
|---|---|---|---|
| 200 | Client consent successfully revoked | - | - |
| 400 | The client ID is blank, or the authorization service reported that the consent was not revoked | ProblemDetail | - |
| 403 | Insufficient permissions to revoke consent | ProblemDetail | - |
| 429 | Too many requests - rate limit exceeded | ProblemDetail | - |
| 503 | Authorization service unavailable | ProblemDetail | - |
| 500 | Internal server error occurred | ProblemDetail | - |
| 405 | The HTTP method is not allowed for this path | ProblemDetail | - |
| 406 | The Accept header does not allow application/json | ProblemDetail | - |
Return type
null (empty response body)
Authorization
HTTP request headers
- Content-Type: Not defined
- Accept: application/json