Table of Contents [+/-]
- 4.1 Account User Names and Passwords
- 4.2 Privileges Provided by MySQL
- 4.3 Grant Tables
- 4.4 Specifying Account Names
- 4.5 Access Control, Stage 1: Connection Verification
- 4.6 Access Control, Stage 2: Request Verification
- 4.7 Adding Accounts, Assigning Privileges, and Dropping Accounts
- 4.8 Reserved Accounts
- 4.9 When Privilege Changes Take Effect
- 4.10 Assigning Account Passwords
- 4.11 Password Management
- 4.12 Password Expiration and Sandbox Mode
- 4.13 Pluggable Authentication
- 4.14 Proxy Users
- 4.15 Account Locking
- 4.16 Setting Account Resource Limits
- 4.17 Troubleshooting Problems Connecting to MySQL
- 4.18 SQL-Based Account Activity Auditing
MySQL enables the creation of accounts that permit client users to
connect to the server and access data managed by the server. The
primary function of the MySQL privilege system is to authenticate a
user who connects from a given host and to associate that user with
privileges on a database such as
DELETE. Additional functionality
includes the ability to grant privileges for administrative
To control which users can connect, each account can be assigned
authentication credentials such as a password. The user interface to
MySQL accounts consists of SQL statements such as
Account Management Statements.
The MySQL privilege system ensures that all users may perform only the operations permitted to them. As a user, when you connect to a MySQL server, your identity is determined by the host from which you connect and the user name you specify. When you issue requests after connecting, the system grants privileges according to your identity and what you want to do.
MySQL considers both your host name and user name in identifying you
because there is no reason to assume that a given user name belongs
to the same person on all hosts. For example, the user
joe who connects from
office.example.com need not be the same person as
joe who connects from
home.example.com. MySQL handles this by enabling
you to distinguish users on different hosts that happen to have the
same name: You can grant one set of privileges for connections by
and a different set of privileges for connections by
see what privileges a given account has, use the
SHOW GRANTS statement. For example:
SHOW GRANTS FOR 'joe'@'office.example.com'; SHOW GRANTS FOR 'joe'@'home.example.com';
Internally, the server stores privilege information in the grant
tables of the
mysql system database. The MySQL
server reads the contents of these tables into memory when it starts
and bases access-control decisions on the in-memory copies of the
MySQL access control involves two stages when you run a client program that connects to the server:
Stage 1: The server accepts or rejects the connection based on your identity and whether you can verify your identity by supplying the correct password.
Stage 2: Assuming that you can
connect, the server checks each statement you issue to determine
whether you have sufficient privileges to perform it. For example,
if you try to select rows from a table in a database or drop a table
from the database, the server verifies that you have the
SELECT privilege for the table or the
DROP privilege for the database.
For a more detailed description of what happens during each stage, see Section 4.5, “Access Control, Stage 1: Connection Verification”, and Section 4.6, “Access Control, Stage 2: Request Verification”. For help in diagnosing privilege-related problems, see Section 4.17, “Troubleshooting Problems Connecting to MySQL”.
If your privileges are changed (either by yourself or someone else) while you are connected, those changes do not necessarily take effect immediately for the next statement that you issue. For details about the conditions under which the server reloads the grant tables, see Section 4.9, “When Privilege Changes Take Effect”.
There are some things that you cannot do with the MySQL privilege system:
You cannot explicitly specify that a given user should be denied access. That is, you cannot explicitly match a user and then refuse the connection.
You cannot specify that a user has privileges to create or drop tables in a database but not to create or drop the database itself.
A password applies globally to an account. You cannot associate a password with a specific object such as a database, table, or routine.