Password Management SET PERSIST password_reuse_interval = 365; SET PERSIST  sets the value for the running MySQL instance. It also saves the value to carry over to subsequent server restarts; see Section 13.7.6.1, “SET Syntax for Variable Assignment” . To change the value for the running MySQL instance without having it carry over to subsequent restarts, use the GLOBAL  keyword rather than  PERSIST . The global password-reuse policy applies to all accounts that have not been set to override it. To establish policy for individual accounts, use the  PASSWORD HISTORY  and  PASSWORD REUSE INTERVAL  options of the  CREATE USER  and  ALTER USER  statements. See Section 13.7.1.3, “CREATE USER Statement” , and Section 13.7.1.1, “ALTER USER Statement” . Example account-specific statements: •Require a minimum of 5 password changes before permitting reuse: CREATE USER ’jeffrey’@’localhost’ PASSWORD HISTORY 5; ALTER USER ’jeffrey’@’localhost’ PASSWORD HISTORY 5; This history-length option overrides the global policy for all accounts named by the statement. CREATE USER ’jeffrey’@’localhost’ PASSWORD REUSE INTERVAL 365 DAY; ALTER USER ’jeffrey’@’localhost’ PASSWORD REUSE INTERVAL 365 DAY; This time-elapsed option overrides the global policy for all accounts named by the statement. These options override both global policy reuse restrictions for all accounts named by the statement. As of MySQL 8.0.13, it is possible to require that attempts to change an account password be verified by specifying the current password to be replaced. This enables DBAs to prevent users from changing a password without proving that they know the current password. Such changes could otherwise occur, for example, if one user walks away from a terminal session temporarily without logging out, and a malicious user uses the session to change the original user’s MySQL password. This can have unfortunate consequences: 1249 •The original user becomes unable to access MySQL until the account password is reset by an administrator. •Defer to the global policy for both types of reuse restrictions: •To combine both types of reuse restrictions, use  PASSWORD HISTORY  and  PASSWORD REUSE INTERVAL  together: •Require a minimum of 365 days elapsed before permitting reuse: CREATE USER ’jeffrey’@’localhost’ PASSWORD HISTORY 5 PASSWORD REUSE INTERVAL 365 DAY; ALTER USER ’jeffrey’@’localhost’ PASSWORD HISTORY 5 PASSWORD REUSE INTERVAL 365 DAY; CREATE USER ’jeffrey’@’localhost’ PASSWORD HISTORY DEFAULT PASSWORD REUSE INTERVAL DEFAULT; ALTER USER ’jeffrey’@’localhost’ PASSWORD HISTORY DEFAULT PASSWORD REUSE INTERVAL DEFAULT; Password Verification-Required Policy