MySQL :: MySQL 8.4 Reference Manual :: 15.7.1.10 SET PASSWORD Statement (original) (raw)

15.7.1.10 SET PASSWORD Statement

SET PASSWORD [FOR user] auth_option
    [REPLACE 'current_auth_string']
    [RETAIN CURRENT PASSWORD]

auth_option: {
    = 'auth_string'
  | TO RANDOM
}

The SET PASSWORD statement assigns a password to a MySQL user account. The password may be either explicitly specified in the statement or randomly generated by MySQL. The statement may also include a password-verification clause that specifies the account current password to be replaced, and a clause that manages whether an account has a secondary password.'_`authstring`_' and'_`currentauthstring`_' each represent a cleartext (unencrypted) password.

Note

Rather than using SET PASSWORD to assign passwords, ALTER USER is the preferred statement for account alterations, including assigning passwords. For example:

ALTER USER user IDENTIFIED BY 'auth_string';

Note

Clauses for random password generation, password verification, and secondary passwords apply only to accounts that use an authentication plugin that stores credentials internally to MySQL. For accounts that use a plugin that performs authentication against a credentials system that is external to MySQL, password management must be handled externally against that system as well. For more information about internal credentials storage, seeSection 8.2.15, “Password Management”.

The REPLACE '_`currentauthstring`_' clause performs password verification. If given:

For more information about password verification by specifying the current password, see Section 8.2.15, “Password Management”.

The RETAIN CURRENT PASSWORD clause implements dual-password capability. If given:

For more information about use of dual passwords, seeSection 8.2.15, “Password Management”.

SET PASSWORD permits these_authoption_ syntaxes:

Important

Under some circumstances, SET PASSWORD may be recorded in server logs or on the client side in a history file such as~/.mysql_history, which means that cleartext passwords may be read by anyone having read access to that information. For information about the conditions under which this occurs for the server logs and how to control it, see Section 8.1.2.3, “Passwords and Logging”. For similar information about client-side logging, seeSection 6.5.1.3, “mysql Client Logging”.

SET PASSWORD can be used with or without a FOR clause that explicitly names a user account:

SET PASSWORD FOR 'jeffrey'@'localhost' = 'auth_string';  
SET PASSWORD = 'auth_string';  

Any client who connects to the server using a nonanonymous account can change the password for that account. (In particular, you can change your own password.) To see which account the server authenticated you as, invoke theCURRENT_USER() function:

SELECT CURRENT_USER();  

If a FOR _`user`_ clause is given, the account name uses the format described inSection 8.2.4, “Specifying Account Names”. For example:

SET PASSWORD FOR 'bob'@'%.example.org' = 'auth_string';

The host name part of the account name, if omitted, defaults to'%'.

SET PASSWORD interprets the string as a cleartext string, passes it to the authentication plugin associated with the account, and stores the result returned by the plugin in the account row in themysql.user system table. (The plugin is given the opportunity to hash the value into the encryption format it expects. The plugin may use the value as specified, in which case no hashing occurs.)

Setting the password for a named account (with aFOR clause) requires theUPDATE privilege for themysql system schema. Setting the password for yourself (for a nonanonymous account with noFOR clause) requires no special privileges.

Statements that modify secondary passwords require these privileges:

When the read_only system variable is enabled, SET PASSWORD requires the CONNECTION_ADMIN privilege (or the deprecatedSUPER privilege), in addition to any other required privileges.

For additional information about setting passwords and authentication plugins, seeSection 8.2.14, “Assigning Account Passwords”, andSection 8.2.17, “Pluggable Authentication”.