Remove one Permission from a Role
Takes one permission out of one role. {id} is the ROLE and {permId} is the PERMISSION — both are slugs, so the order of the two is what tells them apart, and swapping them narrows something nobody asked to narrow.
The batch form, POST /v1/roles/{id}/permissions/remove, does the same for a list.
Removing an existing permission the role does not carry is not an error. On success the response has no body (204).
Failures:
404— the permission does not exist.422 IDE-1066— the permission is declared by a Lerian product, which alone decides the roles that hold it (this includes the M2M permission of a Lerian service’s credential), and it holds the role. 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.503 IDE-0066— the identity provider is unavailable (unreachable, too slow to answer, or failing). Nothing about the request was wrong; retry it later.
DELETE
Remove one Permission from a Role

