1 of 1

mysql.user Table

The mysql.user table stores user account information, global privileges, authentication details, and resource limits.

The mysql.global_priv table has replaced the mysql.user table, and mysql.user should be considered obsolete. It is now a view into mysql.global_priv created for compatibility with older applications and monitoring scripts. New tools are supposed to use INFORMATION_SCHEMA tables. The dedicated mariadb.sys user is created as the definer of the view. Previously, root was the definer, which resulted in privilege problems when this username was changed (MDEV-19650).

The mysql.user table contains information about users that have permission to access the MariaDB server, and their global privileges. The table can be queried and although it is possible to directly update it, it is best to use GRANT and CREATE USER for adding users and privileges.

Note that the MariaDB privileges occur at many levels. A user may not be granted create privilege at the user level, but may still have create permission on certain tables or databases, for example. See for a more complete view of the MariaDB privilege system.

The mysql.user table contains the following fields:

Field

Type

Null

Key

Default

Description

The status variable indicates how many rows the mysql.user table contains where is_role='Y'.

The status variable, indicates how many rows the mysql.user table contains where is_role='N'.

Authentication Plugin

When the plugin column is empty, MariaDB defaults to authenticating accounts with either the or the plugins. It decides which based on the hash used in the value for the Password column. When there's no password set or when the 4.1 password hash is used, (which is 41 characters long), MariaDB uses the plugin. The plugin is used with pre-4.1 password hashes, (which are 16 characters long).

MariaDB also supports the use of alternative . When the plugin column is not empty for the given account, MariaDB uses it to authenticate connection attempts. The specific plugin then uses the value of either the Password column or the authentication_string column to authenticate the user.

A specific authentication plugin can be used for an account by providing the IDENTIFIED VIA authentication_plugin clause with the , , or statements.

For example, the following statement would create an account that authenticates with the :

If the specific authentication plugin uses the authentication_string column, then this value for the account can be specified after a USING or AS keyword. For example, the accepts a that would go into the authentication_string column for the account:

_{This page is licensed: CC BY-SA / Gnu FDL}