Password reset flows in No-Code - Time & Space Complexity

Time Complexity: Password reset flows

O(n)

Understanding Time Complexity

When users reset their passwords, the system performs several steps to verify identity and update credentials.

We want to understand how the time needed grows as more users request password resets.

Scenario Under Consideration

Analyze the time complexity of the following password reset flow.

for each user_request in reset_requests:
    verify user identity
    generate reset token
    send reset email
    wait for user to submit new password
    update password in database
    confirm reset success

This code handles multiple password reset requests one after another, performing verification, token generation, email sending, and updating the password.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through each password reset request.
• How many times: Once per user request, so as many times as there are requests.

How Execution Grows With Input

Each new password reset request adds a similar amount of work.

Input Size (n)	Approx. Operations
10	10 sets of verification, token creation, email sending, and update
100	100 sets of the same operations
1000	1000 sets of the same operations

Pattern observation: The total work grows directly with the number of requests.

Final Time Complexity

Time Complexity: O(n)

This means the time to handle password resets grows in a straight line as more users request resets.

Common Mistake

[X] Wrong: "The system handles all requests instantly no matter how many there are."

[OK] Correct: Each request requires steps like verification and email sending, which take time, so more requests mean more total work.

Interview Connect

Understanding how processes scale with more users helps you design systems that stay responsive and reliable.

Self-Check

"What if the system handled multiple password reset requests at the same time using parallel processing? How would the time complexity change?"

Practice

1. What is the main purpose of a password reset flow in an application?

easy

A. To change the username of the user

B. To delete the user account permanently

C. To help users regain access to their accounts safely

D. To update the user's email address

Solution

1. Step 1: Understand the purpose of password reset

   Password reset flows are designed to help users who forgot their password regain access to their accounts.

2. Step 2: Identify the correct purpose among options

   Only To help users regain access to their accounts safely describes this purpose correctly, while others describe unrelated actions.

3. Final Answer:

   To help users regain access to their accounts safely -> Option C

4. Quick Check:

   Password reset purpose = regain access [OK]

Hint: Password reset helps regain access, not change username [OK]

Common Mistakes:

• Confusing password reset with username change
• Thinking password reset deletes account
• Assuming password reset updates email

2. Which of the following is a common step in a password reset flow?

easy

A. Changing the user's username to 'reset_user'

B. Automatically changing the password without user input

C. Deleting the user account after reset request

D. Sending a reset link or code to the user's email

Solution

1. Step 1: Identify typical password reset steps

   Commonly, a reset link or code is sent to the user's registered email to verify identity.

2. Step 2: Compare options to standard practice

   Only Sending a reset link or code to the user's email matches this standard step; others describe incorrect or harmful actions.

3. Final Answer:

   Sending a reset link or code to the user's email -> Option D

4. Quick Check:

   Reset step = send link/code [OK]

Hint: Reset flows send links or codes, not auto-change passwords [OK]

Common Mistakes:

• Thinking password resets happen without user confirmation
• Believing accounts get deleted after reset
• Confusing username change with password reset

3. In a password reset flow, why is it important that the reset link expires after some time?

medium

A. To prevent unauthorized use if the link is intercepted

B. To allow users to reset password multiple times quickly

C. To make the reset process slower and more secure

D. To automatically change the password after expiration

Solution

1. Step 1: Understand security risks of reset links

   If a reset link never expires, someone who gets it later could misuse it to access the account.

2. Step 2: Identify why expiration helps security

   Expiration limits the time window for misuse, protecting the user's account.

3. Final Answer:

   To prevent unauthorized use if the link is intercepted -> Option A

4. Quick Check:

   Expiration = prevent misuse [OK]

Hint: Expiration stops old links from being misused [OK]

Common Mistakes:

• Thinking expiration slows down the process intentionally
• Believing expiration allows multiple resets quickly
• Assuming password changes automatically after expiration

4. A password reset flow sends a reset code to the user, but the code never expires. What is the main problem with this?

medium

A. The reset code can be reused by attackers anytime

B. Users might forget the code quickly

C. The system will send multiple codes automatically

D. The user cannot reset the password without expiration

Solution

1. Step 1: Analyze the effect of no expiration on reset codes

   If reset codes never expire, anyone who obtains the code can use it anytime to reset the password.

2. Step 2: Identify the security risk

   This creates a security risk because attackers can reuse old codes to access accounts.

3. Final Answer:

   The reset code can be reused by attackers anytime -> Option A

4. Quick Check:

   No expiration = code reuse risk [OK]

Hint: No expiration means codes can be reused by attackers [OK]

Common Mistakes:

• Thinking users forget codes quickly is the main issue
• Assuming system sends codes automatically without request
• Believing expiration prevents password reset entirely

5. You want to design a password reset flow that prevents attackers from guessing reset codes easily. Which approach is best?

hard

A. Use short numeric codes that expire quickly

B. Use long random alphanumeric codes with expiration

C. Send the reset code via public chat for transparency

D. Allow unlimited attempts to enter the reset code

Solution

1. Step 1: Consider code complexity and expiration

   Long random alphanumeric codes are harder to guess than short numeric ones, and expiration limits time for attacks.

2. Step 2: Evaluate options for security

   The approach of using long random alphanumeric codes with expiration combines strong code complexity with time-limited validity, providing optimal security. Other approaches--short numeric codes, unlimited entry attempts, and public code sharing--are vulnerable to guessing, brute-force attacks, or interception.

3. Final Answer:

   Use long random alphanumeric codes with expiration -> Option B

4. Quick Check:

   Strong code + expiration = best security [OK]

Hint: Long random codes with expiration improve security best [OK]

Common Mistakes:

• Choosing short codes that are easy to guess
• Sharing codes publicly reduces security
• Allowing unlimited attempts invites brute force