Why Password policies in MySQL? - Purpose & Use Cases

The Big Idea

What if your database could silently guard your users' passwords for you?

The Scenario

Imagine you manage a website where users create accounts. You ask them to pick passwords by sending emails with rules like "use a number" or "make it long." But you have no way to check if they actually follow these rules before they sign up.

The Problem

Manually checking passwords is slow and messy. You might have to read each password yourself or write complicated code outside the database. This leads to mistakes, weak passwords slipping through, and frustrated users who don't understand why their password was rejected.

The Solution

Password policies in the database let you set clear rules that automatically check passwords when users create or change them. This means the database itself enforces strong passwords, saving you time and keeping accounts safer without extra work.

Before vs After

✗ Before

if length(password) < 8 or not contains_number(password): reject()

✓ After

ALTER USER 'user'@'host' PASSWORD EXPIRE INTERVAL 90 DAY;

What It Enables

It enables automatic, consistent enforcement of strong password rules right where user data lives, making security easier and more reliable.

Real Life Example

A bank's database requires passwords to have at least 12 characters, include uppercase letters, numbers, and symbols. This stops users from choosing weak passwords and protects their money.

Key Takeaways

Manual password checks are slow and error-prone.

Database password policies automate and enforce rules.

This improves security and user experience effortlessly.

Practice

1. What is the purpose of MySQL's validate_password_policy variable?

easy

A. To set rules for creating strong passwords

B. To control user access privileges

C. To define database storage engines

D. To manage query cache size

Solution

1. Step 1: Understand the variable name

   The variable validate_password_policy relates to password validation rules.

2. Step 2: Identify its function

   It sets rules to ensure passwords are strong and secure.

3. Final Answer:

   To set rules for creating strong passwords -> Option A

4. Quick Check:

   Password policy = Set rules for strong passwords [OK]

Hint: Policy variables control password strength rules [OK]

Common Mistakes:

• Confusing password policy with user privileges
• Thinking it manages database storage
• Assuming it controls query cache

2. Which of the following is the correct syntax to check the current password policy level in MySQL?

easy

A. SHOW PASSWORD POLICY;

B. SELECT * FROM validate_password_policy;

C. SHOW VARIABLES LIKE 'validate_password_policy';

D. GET VARIABLES 'validate_password_policy';

Solution

1. Step 1: Recall how to view system variables

   MySQL uses SHOW VARIABLES LIKE 'variable_name'; to display variable values.

2. Step 2: Match the variable name

   The variable for password policy is validate_password_policy, so the correct syntax is SHOW VARIABLES LIKE 'validate_password_policy';

3. Final Answer:

   SHOW VARIABLES LIKE 'validate_password_policy'; -> Option C

4. Quick Check:

   SHOW VARIABLES LIKE 'validate_password_policy' [OK]

Hint: Use SHOW VARIABLES LIKE for system settings [OK]

Common Mistakes:

• Using SELECT on a variable name
• Trying non-existent commands like SHOW PASSWORD POLICY
• Using GET VARIABLES which is invalid syntax

3. Given the following commands executed in MySQL:

SET GLOBAL validate_password_length = 10;
SHOW VARIABLES LIKE 'validate_password_length';

What will be the output of the SHOW VARIABLES command?

medium

A. Variable_name: validate_password_length, Value: 10

B. Variable_name: validate_password_length, Value: 8

C. Syntax error

D. Variable_name: validate_password_policy, Value: 10

Solution

1. Step 1: Understand the SET GLOBAL command

   The command sets the global password length requirement to 10 characters.

2. Step 2: SHOW VARIABLES output

   The SHOW VARIABLES LIKE 'validate_password_length'; will display the current value, which is now 10.

3. Final Answer:

   Variable_name: validate_password_length, Value: 10 -> Option A

4. Quick Check:

   SET GLOBAL changes variable, SHOW displays updated value [OK]

Hint: SET GLOBAL changes variable, SHOW displays current value [OK]

Common Mistakes:

• Expecting default value instead of updated
• Confusing variable names
• Assuming syntax error from SET GLOBAL

4. You tried to set the password policy level with this command:

SET GLOBAL validate_password_policy = 'STRONG';

But MySQL returned an error. What is the likely cause?

medium

A. The command requires quotes around the variable name

B. The variable name is incorrect

C. You must use SET SESSION instead of SET GLOBAL

D. The value should be an integer, not a string

Solution

1. Step 1: Check variable type for validate_password_policy

   This variable expects an integer value (0,1,2) representing policy levels, not strings.

2. Step 2: Understand error cause

   Using a string like 'STRONG' causes a type mismatch error.

3. Final Answer:

   The value should be an integer, not a string -> Option D

4. Quick Check:

   Policy level = integer, not string [OK]

Hint: Policy levels use numbers, not words [OK]

Common Mistakes:

• Using string values instead of integers
• Mistyping variable name
• Confusing SET GLOBAL with SET SESSION

5. You want to enforce a password policy that requires passwords to be at least 12 characters long, include mixed case letters, numbers, and special characters. Which combination of MySQL variables should you set to achieve this?

hard

A. SET GLOBAL validate_password_length = 10; SET GLOBAL validate_password_policy = 0;

B. SET GLOBAL validate_password_length = 12; SET GLOBAL validate_password_policy = 2;

C. SET GLOBAL validate_password_length = 12; SET GLOBAL validate_password_policy = 1;

D. SET GLOBAL validate_password_length = 8; SET GLOBAL validate_password_policy = 0;

Solution

1. Step 1: Understand password length requirement

   You want at least 12 characters, so validate_password_length must be set to 12.

2. Step 2: Understand policy levels

   Policy level 2 (STRONG) requires mixed case, numbers, and special characters.

3. Step 3: Match variables to requirements

   Setting validate_password_policy = 2 and length to 12 enforces all requirements.

4. Final Answer:

   SET GLOBAL validate_password_length = 12; SET GLOBAL validate_password_policy = 2; -> Option B

5. Quick Check:

   Length 12 + policy 2 = strong password rules [OK]

Hint: Policy 2 = strong; length sets minimum characters [OK]

Common Mistakes:

• Using policy 0 or 1 which are weaker
• Setting length less than required
• Confusing policy levels with string values