Grant ABAC Authorization to DMS Users and Roles - Data Management - Alibaba Cloud - Data Management

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

dms:CreateAbacAuthorization

create

*All Resource

*

None

Request parameters

Parameter	Type	Required	Description	Example
IdentityType	string	Yes	The principal type. Valid values: user or custom role. Valid values: USER ROLE	USER
UserId	integer	No	The ID of the user. You can call the GetUser operation to query the user ID. Note If IdentityType is set to USER, this parameter is required.	51****
PolicyId	integer	Yes	The ID of the policy.	12****
RoleId	integer	No	The ID of the role. Note If IdentityType is set to ROLE, this parameter is required.	31****
Tid	integer	No	The ID of the tenant. Note To view the ID of the tenant, go to the Data Management (DMS) console and move the pointer over the profile picture in the upper-right corner. For more information, see the View information about the current tenant section of the "Manage DMS tenants" topic.	3***

Response elements

Element	Type	Description	Example
	object	Schema of Response
RequestId	string	The request ID, which you can use to query logs and troubleshoot issues.	0C1CB646-1DE4-4AD0-B4A4-7D47DD52E931
Success	boolean	Indicates whether the request was successful. true: succeeded. false: failed.	true
ErrorCode	string	The error code.	UnknownError
ErrorMessage	string	The error message.	UnknownError
Result	string	Indicates whether the policy was attached.	true

Examples

Success response

JSON format

{
  "RequestId": "0C1CB646-1DE4-4AD0-B4A4-7D47DD52E931",
  "Success": true,
  "ErrorCode": "UnknownError",
  "ErrorMessage": "UnknownError",
  "Result": "true"
}

Error codes

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.