All Products
Search
Document Center

Resource Management:DetachControlPolicy

Last Updated:Jun 05, 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.

This topic provides an example on how to call the API operation to detach the custom control policy cp-jExXAqIYkwHN**** from the folder fd-ZDNPiT****.

Debugging

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

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • The required resource types are displayed in bold characters.
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
resourcemanager:DetachControlPolicyWrite
  • All Resources
    *
    none
none

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****

For more information about common request parameters, see Common parameters.

Response parameters

ParameterTypeDescriptionExample
object
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.You are not allowed to detach the last access control policy from the object.
404EntityNotExists.TargetThe specified target does not exist in the resource directory.The specified target 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