PolarDB:CreateAccount

The ID of cluster.

The name of the account. The name must meet the following requirements:

• It must start with a lowercase letter and end with a letter or a digit.
• It can contain lowercase letters, digits, and underscores (_).
• It must be 2 to 16 characters in length.
• It cannot be root, admin, or another username that is reserved by the system.

The password of the account. The password must meet the following requirements:

• It must contain at least three of the following character types: uppercase letters, lowercase letters, digits, and special characters.
• It must be 8 to 32 characters in length.
• Special characters include ! @ # $ % ^ & * ( ) _ + - =

The type of the account. Valid values:

• Normal: standard account
• Super: privileged account

• If you leave this parameter empty, the default value Super is used.

• You can create multiple privileged accounts for a PolarDB for Oracle or PolarDB for PostgreSQL cluster. A privileged account is granted more permissions than a standard account. For more information about how to create a database account, see Create a database account.

• You can create only one privileged account for a PolarDB for MySQL cluster. A privileged account is granted more permissions than a standard account. For more information about how to create a database account, see Create a database account.

The description of the account. The description must meet the following requirements:

• It cannot start with http:// or https://.
• It must be 2 to 256 characters in length.

The name of the database that can be accessed by the account. To enter multiple database names, separate the names with commas (,).

The permissions that are granted to the account. Valid values:

• ReadWrite: read and write permissions.
• ReadOnly: read-only permissions.
• DMLOnly: the permissions to execute only DML statements.
• DDLOnly: the permissions to execute only DDL statements.
• ReadIndex: the read-only and index permissions.

• AccountPrivilege is valid only after you specify DBName.

• If multiple database names are specified by the DBName parameter, you must grant permissions on the databases. Separate multiple permissions with commas (,), and make sure that the length of the value of AccountPrivilege does not exceed 900. For example, if you want to grant the account the read and write permissions on DB1 and the read-only permissions on DB2, set DBName to DB1,DB2 and set AccountPrivilege to ReadWrite,ReadOnly.

• This parameter is valid only for standard accounts of PolarDB for MySQL clusters.

The client token that is used to ensure the idempotence of the request. You can use the client to generate the value, but you must make sure that it is unique among different requests. The token can contain only ASCII characters and cannot exceed 64 characters in length. The token is case-sensitive.

Specifies whether to grant the specified account required permissions on all existing databases in the current cluster and databases that will be further created for the current cluster. Valid values:

• 0 or unspecified: does not grant required permissions.
• 1: grants required permissions.

• The parameter is valid only after you configure the AccountPrivilege parameter.

• If you set the parameter to 1, the current account is granted to the required permissions on all databases in the current cluster that are specified by the AccountPrivilege parameter.