mysql system database includes several
grant tables that contain information about user accounts and the
privileges held by them.
Normally, to manipulate the contents of grant tables, you modify
them indirectly by using account-management statements such as
REVOKE to set up accounts and
control the privileges available to each one. See
Section 13.7.1, “Account Management Statements”. The discussion here
describes the underlying structure of the grant tables and how the
server uses their contents when interacting with clients.
mysql database tables contain grant
Other tables in the
mysql database do not hold
grant information and are discussed elsewhere:
server_cost: Optimizer cost estimates. See
Section 8.9.5, “The Optimizer Cost Model”.
event: Information about Event Scheduler
events. See Section 19.4, “Using the Event Scheduler”.
func: Information about user-defined
functions. See Section 23.3, “Adding New Functions to MySQL”.
Used for logging. See Section 5.2, “MySQL Server Logs”.
gtid_executed: Used for replication. See
The mysql.gtid_executed Table.
for server-side help. See
Section 5.1.10, “Server-Side Help”.
innodb_table_stats: Used for
InnoDB persistent optimizer statistics. See
Section 184.108.40.206, “Configuring Persistent Optimizer Statistics Parameters”.
ndb_binlog_index: Used for MySQL Cluster
MySQL Cluster Replication Schema and Tables.
plugin: Information about server plugins.
See Section 220.127.116.11, “Installing and Uninstalling Plugins”, and
Section 23.2, “The MySQL Plugin API”.
proc: Information about stored procedures
and functions. See Section 19.2, “Using Stored Routines (Procedures and Functions)”.
servers: Used by the
FEDERATED storage engine. See
Section 18.104.22.168, “Creating a FEDERATED Table Using CREATE SERVER”.
slave_worker_info: Used for replication.
See Section 17.2.4, “Replication Relay and Status Logs”.
Used for time zone information. See
Section 10.6, “MySQL Server Time Zone Support”.
Each grant table contains scope columns and privilege columns:
Scope columns determine the scope of each row in the tables;
that is, the context in which the row applies. For example, a
user table row with
User values of
'bob' applies to authenticating connections
made to the server from the host
thomas.loc.gov by a client that specifies a
user name of
bob. Similarly, a
db table row with
bob connects from the host
thomas.loc.gov to access the
reports database. The
columns_priv tables contain scope columns
indicating tables or table/column combinations to which each
row applies. The
procs_priv scope columns
indicate the stored routine to which each row applies.
Privilege columns indicate which privileges a table row grants; that is, which operations it permits to be performed. The server combines the information in the various grant tables to form a complete description of a user's privileges. Section 6.2.5, “Access Control, Stage 2: Request Verification”, describes the rules for this.
The server uses the grant tables in the following manner:
user table scope columns determine
whether to reject or permit incoming connections. For
permitted connections, any privileges granted in the
user table indicate the user's global
privileges. Any privileges granted in this table apply to
all databases on the server.
db table scope columns determine which
users can access which databases from which hosts. The
privilege columns determine the permitted operations. A
privilege granted at the database level applies to the
database and to all objects in the database, such as tables
and stored programs.
columns_priv tables are similar to the
db table, but are more fine-grained: They
apply at the table and column levels rather than at the
database level. A privilege granted at the table level applies
to the table and to all its columns. A privilege granted at
the column level applies only to a specific column.
procs_priv table applies to stored
routines (procedures and functions). A privilege granted at
the routine level applies only to a single procedure or
proxies_priv table indicates which
users can act as proxies for other users and whether a user
can grant the
to other users.
The server uses the
db tables in the
database at both the first and second stages of access control
(see Section 6.2, “The MySQL Access Privilege System”). The columns in the
db tables are shown
Table 6.3 user and db Table Columns
|Resource control columns|
authentication_string columns store
authentication plugin and credential information. In MySQL 5.7.6,
Password column was removed and all
credentials are stored in the
If an account row names a plugin in the
column, the server uses it to authenticate connection attempts for
the account. It is up to the plugin whether it uses the
authentication_string column values.
As of MySQL 5.7.2, the
plugin column must be
Before MySQL 5.7.2, the
plugin column for an
account row is permitted to be empty. In this case, the server
authenticates the account using the
mysql_old_password plugin implicitly, depending
on the format of the password hash in the
Password column. If the
Password value is empty or a 4.1 password hash
(41 characters), the server uses
mysql_native_password. If the password value is
a pre-4.1 password hash (16 characters), the server uses
mysql_old_password. (For additional information
about these hash formats, see Section 22.214.171.124, “Password Hashing in MySQL”.)
Clients must match the password in the
column of the account row.
At startup, and at runtime when
is executed, the server checks
user table rows.
As of MySQL 5.7.2, for any row with an empty
plugin column, the server writes a warning to
the error log of this form:
[Warning] User entry '
host_name' has an empty plugin value. The user will be ignored and no one can login with this user anymore.
To address this problem, see Section 126.96.36.199, “Migrating Away from Pre-4.1 Password Hashing and the mysql_old_password Plugin”.
password_expired column permits DBAs to
expire account passwords and require users to reset their
password. The default
password_expired value is
'N', but can be set to
ALTER USER statement.
After an account's password has been expired, all operations
performed by the account in subsequent connections to the server
result in an error until the user issues an
ALTER USER statement (for MySQL
5.7.6 and up) or
statement (before MySQL 5.7.6) to establish a new account
It is possible after password expiration to “reset” a password by setting it to its current value. As a matter of good policy, it is preferable to choose a different password.
password_last_changed (added in MySQL 5.7.4) is
TIMESTAMP column indicating when the password
was last changed. The value is non-
for accounts that use MySQL built-in authentication methods
(accounts that use an authentication plugin of
sha256_password). The value is
NULL for other accounts, such as those
authenticated using an external authentication system.
password_lifetime (added in MySQL 5.7.4)
indicates the account password lifetime, in days. If the password
is past its lifetime (assessed using the
password_last_changed column), the server
considers the password expired when clients connect using the
account. A value of
N greater than zero
means that the password must be changed every
N days. A value of 0 disables automatic
password expiration. If the value is
default), the global expiration policy applies, as defined by the
account_locked (added in MySQL 5.7.6) indicates
whether the account is locked (see
Section 6.3.11, “User Account Locking”).
During the second stage of access control, the server performs
request verification to ensure that each client has sufficient
privileges for each request that it issues. In addition to the
db grant tables,
the server may also consult the
columns_priv tables for requests that involve
tables. The latter tables provide finer privilege control at the
table and column levels. They have the columns shown in the
Table 6.4 tables_priv and columns_priv Table Columns
columns are set to the current timestamp and the
CURRENT_USER value, respectively,
but are otherwise unused.
For verification of requests that involve stored routines, the
server may consult the
procs_priv table, which
has the columns shown in the following table.
Table 6.5 procs_priv Table Columns
Routine_type column is an
ENUM column with values of
indicate the type of routine the row refers to. This column
enables privileges to be granted separately for a function and a
procedure with the same name.
columns are unused.
proxies_priv table records information
about proxy accounts. It has these columns:
For an account to be able to grant the
PROXY privilege to other accounts,
it must have a row in the
With_grant set to 1 and
Proxied_user set to indicate the account or
accounts for which the privilege can be granted. For example, the
'root'@'localhost' account created during MySQL
installation has a row in the
table that enables granting the
PROXY privilege for
''@'', that is, for all users and all hosts.
root to set up proxy users, as
well as to delegate to other accounts the authority to set up
proxy users. See Section 6.3.10, “Proxy Users”.
Scope columns in the grant tables contain strings. They are declared as shown here; the default value for each is the empty string.
Table 6.6 Grant Table Scope Column Types
For access-checking purposes, comparisons of
Table_name values are case sensitive.
Routine_name values are not case sensitive.
db tables list
each privilege in a separate column that is declared as
ENUM('N','Y') DEFAULT 'N'. In other words, each
privilege can be disabled or enabled, with the default being
tables declare the privilege columns as
SET columns. Values in these
columns can contain any combination of the privileges controlled
by the table. Only those privileges listed in the column value are
Table 6.7 Set-Type Privilege Column Values
|Table Name||Column Name||Possible Set Elements|
user table specifies administrative
privileges, such as
SHUTDOWN. Administrative operations
are operations on the server itself and are not database-specific,
so there is no reason to list these privileges in the other grant
tables. Consequently, the server need consult only the
user table to determine whether a user can
perform an administrative operation.
FILE privilege also is
specified only in the
user table. It is not an
administrative privilege as such, but a user's ability to read or
write files on the server host is independent of the database
The server reads the contents of the grant tables into memory when
it starts. You can tell it to reload the tables by issuing a
statement or executing a mysqladmin
flush-privileges or mysqladmin reload
command. Changes to the grant tables take effect as indicated in
Section 6.2.6, “When Privilege Changes Take Effect”.
When you modify an account, it is a good idea to verify that your
changes have the intended effect. To check the privileges for a
given account, use the
statement. For example, to determine the privileges that are
granted to an account with user name and host name values of
use this statement:
SHOW GRANTS FOR 'bob'@'pc84.example.com';
To display nonprivilege properties of an account, use
SHOW CREATE USER:
SHOW CREATE USER 'bob'@'pc84.example.com';