Modify user privileges on a database by calling ModifyDatabaseUserRoles - ApsaraDB for OceanBase (Deprecated) - Alibaba Cloud - ApsaraDB for OceanBase (Deprecated)

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

oceanbase:ModifyDatabaseUserRoles

update

*All Resource

*

None

Request parameters

Parameter	Type	Required	Description	Example
DatabaseName	string	Yes	The ID of the tenant.	sms_pre
TenantId	string	Yes	A list of usernames and their respective roles.	t4louaeei****
Users	string	Yes	The ID of the OceanBase cluster.	[{"UserName":"oceanbase1","Role":"readwrite"},{"UserName":"oceanbase2","Role":"readonly"}]
InstanceId	string	No	The account information.	ob317v4uif****

Response elements

Element	Type	Description	Example
	object	The ID of the tenant.
TenantUser	object	The name of the database.
DatabaseName	string	Example 1	sms_pre
Users	array<object>	List of accounts granted permissions on the database.
	object	You can call this operation to modify the privileges of an account on a database.
Role	string	Role permission assigned to the account for this database. For MySQL mode, roles are defined at the database level and include the following types: ReadWrite: read-write permission, including ALL PRIVILEGES; ReadOnly: read-only permission, including SELECT; DDL: DDL permission, including CREATE, DROP, ALTER, SHOW VIEW, CREATE VIEW; DML: DML permission, including SELECT, INSERT, UPDATE, DELETE, SHOW VIEW.	ReadOnly
UserName	string	Account name.	user_pay_ro
TenantId	string	Tenant ID.	t33h8y08k****
RequestId	string	Request ID.	EE205C00-30E4-XXXX-XXXX-87E3A8A2AA0C

Examples

Success response

JSON format

{
  "TenantUser": {
    "DatabaseName": "sms_pre",
    "Users": [
      {
        "Role": "ReadOnly",
        "UserName": "user_pay_ro"
      }
    ],
    "TenantId": "t33h8y08k****"
  },
  "RequestId": "EE205C00-30E4-XXXX-XXXX-87E3A8A2AA0C"
}

Error codes

HTTP status code	Error code	Error message	Description
2014	InternalError	The request processing has failed due to some unknown error.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.