Revoke RBAC Permissions & Secure Cluster Access via CleanUserPermissions - ACK - Alibaba Cloud - Container Service for Kubernetes

You can call the CleanUserPermissions operation to delete the kubeconfig files of the specified users and revoke the relevant Role-Based Access Control (RBAC) permissions. This API operation is suitable for scenarios where employees have resigned or the accounts of employees are locked.

Operation description

Note

To call this operation, make sure that you have the AliyunCSFullAccess permission.
You cannot revoke the permissions of an Alibaba Cloud account.
You cannot revoke the permissions of the account that you use to call this operation.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

cs:CleanUserPermissions

none

*All Resource

*

None

Request syntax

DELETE /users/{Uid}/permissions HTTP/1.1

Path Parameters

Parameter	Type	Required	Description	Example
Uid	string	Yes	The ID of the specified Resource Access Management (RAM) user or RAM role within the Alibaba Cloud account.	26562443851650****

Request parameters

Parameter	Type	Required	Description	Example
Force	boolean	No	Specifies whether to forcefully delete the specified kubeconfig files. Valid values: false (default): checks the cluster access records within the previous seven days before deleting the kubeconfig files. The kubeconfig files are not deleted if cluster access records are found or fail to be retrieved. true: forcefully deletes the kubeconfig files without checking the cluster access records.	false
ClusterIds	array	No	The cluster IDs. If you specify a list of cluster IDs, only the kubeconfig files and RBAC permissions of the clusters that belong to the current user in the list are revoked.
	string	No	The ID of the cluster.	cd53c3a9ee12a494c9a0451e2ffc11c65

Response elements

Element	Type	Description	Example
	object
request_id	string	The request ID.	687C5BAA-D103-4993-884B-C35E4314****
task_id	string	The task ID.	clean-user-permissions-2085266204******-6694c16e6ae07*********

Examples

Success response

JSON format

{
  "request_id": "687C5BAA-D103-4993-884B-C35E4314****",
  "task_id": "clean-user-permissions-2085266204********-6694c16e6ae07***********"
}

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.