ApplicableOperations
Entity - Role Based Access Control - Interrogates the SecurableType table in the database
Verb | Request | Notes | Permissions required |
|---|---|---|---|
GET - by securable type id | /Consumer/ApplicableOperations/SecurableTypeId/{securableTypeId} | Gets list of all available applicable operations for the securable type by its id |
Returns Unauthorized (401) if user does not have the required permissions. |
GET - by securable type name | /Consumer /ApplicableOperations/SecurableTypeName/{securableTypeName} | Gets list of all available applicable operations for the securable type by its name |
Returns Unauthorized (401) if user does not have the required |
POST | /Consumer /ApplicableOperations | Creates an applicable operation. Payload should include securable type id or name. Using both causes ambiguity in the Consumer API which will not try to set any priority over which one to use and return a Bad Request (400) HTTP status. Example Request - securable type id {
"OperationName":"Operation",
"SecurableTypeId":8
}Example Request - securable type name {
"OperationName":"Operation",
"SecurableTypeName":"SecurableType"
} |
Returns Unauthorized (401) if user does not have the required |
DELETE | /Consumer /ApplicableOperations/{id} | Deletes applicable operation by id |
Returns Unauthorized (401) if user does not have the required |