Account Management Statements is  0  (the default), the server determines the number of simultaneous connections for the account from the global value of the  max_user_connections  system variable. If  max_user_connections  is also zero, there is no limit for the account. Example: ALTER USER ’jeffrey’@’localhost’ WITH MAX_QUERIES_PER_HOUR 500 MAX_UPDATES_PER_HOUR 100; ALTER USER Password-Management Options ALTER USER  supports several  password_option  values for password management: •Password expiration options: You can expire an account password manually and establish its password expiration policy. Policy options do not expire the password. Instead, they determine how the server applies automatic expiration to the account based on password age, which is assessed from the date and time of the most recent account password change. •Password reuse options: You can restrict password reuse based on number of password changes, time elapsed, or both. •Password verification-required options: You can indicate whether attempts to change an account password must specify the current password, as verification that the user attempting to make the change actually knows the current password. •Incorrect-password failed-login tracking options: You can cause the server to track failed login attempts and temporarily lock accounts for which too many consecutive incorrect passwords are given. The required number of failures and the lock time are configurable. This section describes the syntax for password-management options. For information about establishing policy for password management, see Section 6.2.15, “Password Management” . If multiple password-management options of a given type are specified, the last one takes precedence. For example,  PASSWORD EXPIRE DEFAULT PASSWORD EXPIRE NEVER  is the same as  PASSWORD EXPIRE NEVER . Note Except for the options that pertain to failed-login tracking, password-management options 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, see Section 6.2.15, “Password Management” . A client has an expired password if the account password was expired manually or the password age is considered greater than its permitted lifetime per the automatic expiration policy. In this case, the server either disconnects the client or restricts the operations permitted to it (see Section 6.2.16, “Server Handling of Expired Passwords” ). Operations performed by a restricted client result in an error until the user establishes a new account password. Note Although it is possible to “reset”  an expired password by setting it to its current value, it is preferable, as a matter of good policy, to choose a different password. 2846