Unassign a role from a clientAdded in 8.8

DELETE 
/roles/:roleId/clients/:clientId

Strongly Consistent About endpoint data consistency

Unassigns the specified role from the client. The client will no longer inherit the authorizations associated with this role.

Required permissions

When authorization is enabled, this endpoint requires the following permission. See resources and permissions to learn more.

Resource type	Permission
ROLE	UPDATE

Request

Responses

204

The role was unassigned successfully from the client.

400

The provided data is not valid.

403

Forbidden. The request is not allowed.

404

The role or client with the given ID or username was not found.

500

An internal error occurred while processing the request.

503

The service is currently unavailable. This may happen only on some requests where the system creates backpressure to prevent the server's compute resources from being exhausted, avoiding more severe failures. In this case, the title of the error object contains RESOURCE_EXHAUSTED. Clients are recommended to eventually retry those requests after a backoff period. You can learn more about the backpressure mechanism here: https://docs.camunda.io/docs/components/zeebe/technical-concepts/internal-processing/#handling-backpressure .