All Products
Search
Document Center

Resource Management:DetachControlPolicy

Last Updated:Jun 25, 2024

Detaches an access control policy.

Operation description

After you detach an access control policy, the operations performed on resources by using members are not limited by the policy. Make sure that the detached policy meets your expectations. Otherwise, your business may be affected.

Both the system and custom access control policies can be detached. If an object has only one access control policy attached, the policy cannot be detached.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

Authorization information

There is currently no authorization information disclosed in the API.

Request parameters

ParameterTypeRequiredDescriptionExample
PolicyIdstringYes

The ID of the access control policy.

cp-jExXAqIYkwHN****
TargetIdstringYes

The ID of the object from which you want to detach the access control policy. Access control policies can be attached to the following objects:

  • Root folder
  • Subfolders of the Root folder
  • Members
fd-ZDNPiT****

Response parameters

ParameterTypeDescriptionExample
object

The returned result.

RequestIdstring

The ID of the request.

9EA4F962-1A2E-4AFE-BE0C-B14736FC46CC

Examples

Sample success responses

JSONformat

{
  "RequestId": "9EA4F962-1A2E-4AFE-BE0C-B14736FC46CC"
}

Error codes

HTTP status codeError codeError messageDescription
400NotSupport.DetachLastControlPolicyIt is not detach the last control policy on the target node.-
404EntityNotExists.TargetThe specified target does not exist in the resource directory.The specified object does not exist in the resource directory.

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
No change history