Contents
Entity - Role Based Access Control - Interrogates the SecurableType table in the database
| Verb | URL | Notes | Permissions Required |
|---|---|---|---|
| GET - by securable type id | http://<myserver>/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 | http://<myserver>/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 | http://<myserver>/consumer /ApplicableOperations | Creates an applicable operation. Request payload: Request Payload - securable type id {
"OperationName":"Operation",
"SecurableTypeId":8
}
Or Request Payload - securable type name {
"OperationName":"Operation",
"SecurableName":"SecurableType"
}
Either securable type id or name can be used. Using both results in ambiguous situation. Consumer API will not try to set any priority over which one to use and would return Bad Request (400) HTTP status. |
Returns Unauthorized (401) if user does not have the required |
| DELETE | http://<myserver>/consumer /ApplicableOperations/{id} | Deletes applicable operation by id |
Returns Unauthorized (401) if user does not have the required |