Authentication with requirepass in Redis - Time & Space Complexity

Time Complexity: Authentication with requirepass

O(n)

Understanding Time Complexity

When Redis requires a password, it checks the password each time a client connects. Understanding how this check grows with more clients helps us see if it slows down as more people connect.

We want to know: How does the time to verify a password change as more clients try to connect?

Scenario Under Consideration

Analyze the time complexity of the following Redis authentication commands.

CONFIG SET requirepass mysecret

# Client tries to authenticate
AUTH mysecret

# Server checks password
# If correct, client is allowed commands
# If wrong, connection is rejected
    

This snippet sets a password and shows how clients authenticate by sending the password to Redis, which checks it before allowing commands.

Identify Repeating Operations

Look for repeated actions that affect time.

• Primary operation: Password comparison for each client authentication.
• How many times: Once per client connection that sends AUTH.

How Execution Grows With Input

Each time a client connects and sends a password, Redis compares it to the stored password.

Input Size (n)	Approx. Operations
10 clients	10 password checks
100 clients	100 password checks
1000 clients	1000 password checks

Pattern observation: The number of password checks grows directly with the number of clients trying to authenticate.

Final Time Complexity

Time Complexity: O(n)

This means the total time to handle authentication grows in a straight line as more clients connect and authenticate.

Common Mistake

[X] Wrong: "Checking the password takes longer as the password gets longer or more clients connect at once."

[OK] Correct: Redis compares the password in a simple way that takes about the same time regardless of password length, and each check is independent per client, so more clients just add more checks, not slower checks.

Interview Connect

Understanding how authentication scales helps you explain how systems stay fast even when many users connect. This skill shows you can think about real-world system behavior clearly.

Self-Check

"What if Redis stored multiple passwords for different users? How would the time complexity of authentication change?"

Practice

1. What does the requirepass directive do in Redis?

easy

A. It sets a password that clients must use to authenticate before accessing Redis.

B. It disables all client connections to Redis.

C. It automatically encrypts all data stored in Redis.

D. It sets the maximum number of clients allowed to connect.

Solution

1. Step 1: Understand the purpose of requirepass

   The requirepass directive is used to protect Redis by requiring clients to authenticate with a password.

2. Step 2: Compare options with this purpose

   Only It sets a password that clients must use to authenticate before accessing Redis. describes setting a password for client authentication, matching the purpose of requirepass.

3. Final Answer:

   It sets a password that clients must use to authenticate before accessing Redis. -> Option A

4. Quick Check:

   requirepass = password protection [OK]

Hint: requirepass means password required to connect [OK]

Common Mistakes:

• Thinking requirepass disables connections
• Confusing requirepass with encryption
• Assuming requirepass limits client count

2. Which of the following is the correct way to authenticate a Redis client after requirepass is set?

easy

A. AUTH mypassword

B. LOGIN mypassword

C. CONNECT mypassword

D. PASSWORD mypassword

Solution

1. Step 1: Identify the Redis command for authentication

   Redis uses the AUTH command followed by the password to authenticate clients.

2. Step 2: Check the options for the AUTH command

   Only AUTH mypassword uses the correct AUTH command syntax.

3. Final Answer:

   AUTH mypassword -> Option A

4. Quick Check:

   AUTH command = authenticate password [OK]

Hint: Use AUTH command to send password [OK]

Common Mistakes:

• Using LOGIN instead of AUTH
• Using CONNECT or PASSWORD commands which don't exist
• Forgetting to include the password after AUTH

3. Given the Redis configuration has requirepass foobar set, what will be the output of the following commands sequence?

SET key1 value1
GET key1
AUTH foobar
GET key1

medium

A. OK
(error) NOAUTH Authentication required.
OK
"value1"

B. OK
"value1"
OK
"value1"

C. OK
(error) NOAUTH Authentication required.
(error) NOAUTH Authentication required.
"value1"

D. (error) NOAUTH Authentication required.
(error) NOAUTH Authentication required.
OK
(nil)

Solution

1. Step 1: Understand requirepass effect on commands

   When requirepass is set, all commands except AUTH fail with NOAUTH error until the client authenticates.

2. Step 2: Analyze command sequence

   SET key1 value1 fails with NOAUTH (unauthenticated). GET key1 fails with NOAUTH. AUTH foobar succeeds (OK). GET key1 returns (nil) because the key was never successfully set.

3. Final Answer:

   (error) NOAUTH Authentication required. (error) NOAUTH Authentication required. OK (nil) -> Option D

4. Quick Check:

   Pre-AUTH: NOAUTH errors; post-AUTH: (nil) since key unset [OK]

Hint: Non-AUTH commands fail with NOAUTH before successful AUTH [OK]

Common Mistakes:

• Assuming commands work before AUTH
• Thinking AUTH returns error
• Confusing order of outputs

4. You set requirepass mysecret in your Redis config. A client tries to run AUTH wrongpass followed by GET key. What is the problem and how to fix it?

medium

A. The client must restart Redis; fix by restarting server.

B. The client used wrong password; fix by using correct password with AUTH.

C. requirepass disables GET command; fix by removing requirepass.

D. The client must run AUTH after GET; fix by swapping commands.

Solution

1. Step 1: Identify the error cause

   Using a wrong password with AUTH means client is not authenticated, so GET command will fail with NOAUTH error.

2. Step 2: Correct the authentication process

   Client must provide the correct password with AUTH to authenticate and access commands like GET.

3. Final Answer:

   The client used wrong password; fix by using correct password with AUTH. -> Option B

4. Quick Check:

   Wrong password = no access; correct password fixes it [OK]

Hint: AUTH password must match requirepass exactly [OK]

Common Mistakes:

• Trying commands before successful AUTH
• Thinking requirepass disables commands permanently
• Restarting server unnecessarily

5. You want to change the Redis password without restarting the server. Which command should you use to set a new password newpass123 dynamically?

hard

A. AUTH newpass123

B. SET requirepass newpass123

C. CONFIG SET requirepass newpass123

D. CONFIG GET requirepass

Solution

1. Step 1: Understand how to change requirepass dynamically

   Redis allows changing configuration parameters at runtime using CONFIG SET command.

2. Step 2: Identify correct command to change password

   To change the password, use CONFIG SET requirepass newpass123. AUTH is for client login, SET is for keys, CONFIG GET only reads.

3. Final Answer:

   CONFIG SET requirepass newpass123 -> Option C

4. Quick Check:

   CONFIG SET changes config without restart [OK]

Hint: Use CONFIG SET requirepass to change password live [OK]

Common Mistakes:

• Using AUTH to change password
• Trying SET command for config
• Using CONFIG GET which only reads