Remove Permissions from a User in Batch

Revokes several direct grants, naming them in the body.

It is a POST rather than a DELETE because the permissions travel in a request body; DELETE /v1/users/{id}/permissions/{permId} does the same for exactly one.

Only the DIRECT grant goes. If the same permission also reaches the person through a role or a group, they keep it and the call still answers 204 — check GET /v1/users/{id}/effective-permissions afterwards if the intent was to take the ability away. Revoking a permission the person does not hold directly is not an error. On success the response has no body (204).

Failures:

• 400 — permissions is missing or empty.
• 503 IDE-0066 — the identity provider is unavailable (unreachable, too slow to answer, or failing). Nothing about the request was wrong; retry it later.

POST /v1/users/{id}/permissions/remove

Remove Permissions from a User in Batch

cURL

curl --request POST \
  --url https://identity.sandbox.lerian.net/v1/users/{id}/permissions/remove \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "permissions": [
    "<string>"
  ]
}
'

400

{
  "code": "<string>",
  "entityType": "<string>",
  "err": "<unknown>",
  "message": "<string>",
  "title": "<string>"
}

Authorizations

Authorization · string · header · required

JWT bearer token issued by the identity provider.

Path Parameters

id · string · required

User ID.

Example:

"00000000-0000-0000-0000-000000000000"

Body

application/json

The permissions to revoke from the user.

permissions · string[] · required

Permission identifiers.

Minimum array length: 1

Response

204

No Content