Delete a Policy

Delete the policy identified by the <namespace>/<policyName> pair in the topic field.

Command

Field Value
topic <namespace>/<policyName>/policies/commands/delete
path /

Response

Field   Value
topic   <namespace>/<policyName>/policies/commands/delete
path   /
status code  
  204 Success - The Policy was successfully deleted.

Example: Delete a Policy

Delete a Policy entry

Deletes a Policy entry identified by the <namespace>/<policyName> pair in the topic field and the <label> in the path field.

Command

Field Value
topic <namespace>/<policyName>/policies/commands/delete
path /entries/<label>

Response

Field   Value
topic   <namespace>/<policyName>/policies/commands/delete
path   /entries/<label>
status code  
  204 Success - The Policy entry was successfully deleted.

Example: Delete a Policy entry

Delete a single resource

Deletes the resource identified by the <namespace>/<policyName> pair in the topic field and the <label> and <resource> in the path field.

Command

Field Value
topic <namespace>/<policyName>/policies/commands/delete
path /entries/<label>/resources/<resource>

Response

Field   Value
topic   <namespace>/<policyName>/policies/commands/delete
path   /entries/<label>/resources/<resource>
status code  
  204 Success - The resource was successfully deleted.

Example: Delete a resource

Delete a single subject

Delete the subject identified by the <namespace>/<policyName> pair in the topic field and the <label> and <subjectId> in the path field.

Command

Field Value
topic <namespace>/<policyName>/policies/commands/delete
path /entries/<label>/subjects/<subjectId>

Response

Field   Value
topic   <namespace>/<policyName>/policies/commands/delete
path   /entries/<label>/subjects/<subjectId>
status code  
  204 Success - The subject was successfully deleted.

Example: Delete a subject

Common errors

status Value
400 Bad Format - The request could not be completed due to malformed request syntax.
401 Unauthorized - The request could not be completed due to missing authentication.
403 Forbidden - The Policy could not be modified as the requester had insufficient permissions (‘WRITE’ is required).
404 Not Found - The request could not be completed. The Policy with the given ID was not found in the context of the authenticated user.
412 Precondition Failed - A precondition for reading or writing the (sub-)resource failed. This will happen for write requests, if you specified an If-Match or If-None-Match header, which fails the precondition check against the current ETag of the (sub-)resource.
413 Request Entity Too Large - The created or modified entity is larger than the accepted limit of 100 kB.
  See Policy Error Responses for examples of other error responses.
Tags: protocol