Remove Permissions from a Role in Batch

Narrows a role by several permissions at once, naming them in the body.

It is a POST rather than a DELETE because the permissions travel in a request body; DELETE /v1/roles/{id}/permissions/{permId} does the same for exactly one. Both exist and both are supported.

Removing an existing permission the role does not carry is not an error. On success the response has no body (204).

Failures:

• 400 — permissions is missing or empty.
• 404 — one of the permissions does not exist.
• 422 IDE-1066 — a permission holding the role is declared by a Lerian product, which alone decides the roles that hold it; the message names it. Change who has the access by adding or removing people on the role, or in a group it is granted to; a machine permission has no client-side change. Permissions earlier in the list are already removed.
• 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/roles/{id}/permissions/remove

Remove Permissions from a Role in Batch

cURL

curl --request POST \
  --url https://identity.sandbox.lerian.net/v1/roles/{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

Role ID.

Example:

"midaz-editor"

Body

application/json

The permissions to remove from the role.

permissions · string[] · required

Permission identifiers.

Minimum array length: 1

Response

204

No Content