Password reset email pattern in Flask - Mini Project: Build & Apply

Password Reset Email Pattern in Flask

📖 Scenario: You are building a simple Flask web app that allows users to reset their password by sending them a reset email link.This is a common feature in many websites where users can request a password reset if they forget their password.

🎯 Goal: Build a Flask route that sends a password reset email using a predefined email pattern.The email should include a reset link with a token for security.

📋 What You'll Learn

Create a Flask app with a route to handle password reset requests

Define a user email dictionary with sample users

Create a function to generate a reset token

Send an email message with the reset link using the token

💡 Why This Matters

🌍 Real World

Password reset is a critical feature in web applications to help users regain access securely.

💼 Career

Understanding how to implement password reset flows is important for backend web developers and security-conscious programmers.

1

Set up user email data

Create a dictionary called users with these exact entries: '[e-mail]': 'Alice', '[e-mail]': 'Bob', and '[e-mail]': 'Carol'.

Flask

# Your code here

Hint

Use a Python dictionary with the exact keys and values given.

2

Configure Flask app and secret key

Import Flask and request from flask. Create a Flask app instance called app. Then create a variable called SECRET_KEY and set it to the string 'mysecretkey'.

Flask

users = {
    '[e-mail]': 'Alice',
    '[e-mail]': 'Bob',
    '[e-mail]': 'Carol'
}
# Your code here

Hint

Import Flask and request, then create app and secret key variables exactly as shown.

3

Create token generation function

Define a function called generate_token that takes an email parameter and returns a string combining the email and SECRET_KEY separated by a dash. Use an f-string for formatting.

Flask

users = {
    '[e-mail]': 'Alice',
    '[e-mail]': 'Bob',
    '[e-mail]': 'Carol'
}

from flask import Flask, request
app = Flask(__name__)
SECRET_KEY = 'mysecretkey'

# Your code here

Hint

Use a function with one parameter and return the combined string using an f-string.

4

Create password reset route to send email

Create a Flask route @app.route('/reset_password', methods=['POST']). Define a function called reset_password that gets the email from request.form. If the email is in users, generate a token using generate_token(email). Then create a variable reset_link with the value f"http://example.com/reset?token={token}". Finally, create a variable email_message with the exact string f"Hi {users[email]}, click here to reset your password: {reset_link}".

Flask

users = {
    '[e-mail]': 'Alice',
    '[e-mail]': 'Bob',
    '[e-mail]': 'Carol'
}

from flask import Flask, request
app = Flask(__name__)
SECRET_KEY = 'mysecretkey'

def generate_token(email):
    return f"{email}-{SECRET_KEY}"

# Your code here

Hint

Use Flask route decorator and request.form.get to get email. Use the generate_token function and build the reset link and message exactly as shown.

Practice

1. What is the main purpose of using a token in a Flask password reset email pattern?

easy

A. To securely verify the user's identity before allowing password reset

B. To store the user's new password temporarily

C. To send the user's password in plain text via email

D. To log the user out of all sessions automatically

Solution

1. Step 1: Understand the role of tokens in password reset

   Tokens are unique codes sent to users to confirm their identity securely during password reset.

2. Step 2: Identify the purpose of the token

   The token ensures only the rightful user can reset the password by verifying their identity.

3. Final Answer:

   To securely verify the user's identity before allowing password reset -> Option A

4. Quick Check:

   Token = Secure identity verification [OK]

Hint: Tokens verify identity safely before password changes [OK]

Common Mistakes:

• Thinking tokens store passwords
• Assuming tokens send passwords in email
• Believing tokens log users out

2. Which of the following is the correct way to create a timed token using Flask's itsdangerous library?

easy

A. token = URLSafeTimedSerializer.dumps(secret_key, email)

B. token = URLSafeTimedSerializer(secret_key).loads(email)

C. serializer = URLSafeTimedSerializer(); token = serializer.dumps(secret_key, email)

D. serializer = URLSafeTimedSerializer(secret_key); token = serializer.dumps(email)

Solution

1. Step 1: Recall the correct usage of URLSafeTimedSerializer

   It requires initializing with a secret key, then calling dumps() with the data to encode.

2. Step 2: Match the syntax to the correct option

   serializer = URLSafeTimedSerializer(secret_key); token = serializer.dumps(email) correctly creates the serializer and calls dumps(email) to create the token.

3. Final Answer:

   serializer = URLSafeTimedSerializer(secret_key); token = serializer.dumps(email) -> Option D

4. Quick Check:

   Serializer + dumps(data) = token [OK]

Hint: Initialize serializer with key, then dumps(data) for token [OK]

Common Mistakes:

• Calling dumps as a static method
• Passing secret key to dumps instead of constructor
• Using loads instead of dumps to create token

3. Given this Flask code snippet, what will be printed if the token is valid and not expired?

from itsdangerous import URLSafeTimedSerializer
serializer = URLSafeTimedSerializer('secret')
token = serializer.dumps('[e-mail]')

try:
    email = serializer.loads(token, max_age=3600)
    print(email)
except Exception:
    print('Invalid or expired token')

medium

A. None

B. [e-mail]

C. secret

D. Invalid or expired token

Solution

1. Step 1: Understand what serializer.dumps and loads do

   dumps creates a token from the email string; loads decodes it back if valid and within max_age.

2. Step 2: Analyze the try-except block

   If the token is valid and not expired, loads returns the original email, which is printed.

3. Final Answer:

   [e-mail] -> Option B

4. Quick Check:

   Valid token returns original email [OK]

Hint: Valid loads returns original data, else error [OK]

Common Mistakes:

• Assuming loads returns the secret key
• Confusing dumps and loads output
• Ignoring max_age expiration

4. Identify the error in this Flask password reset token verification code:

from itsdangerous import URLSafeTimedSerializer
serializer = URLSafeTimedSerializer('secret')
token = serializer.dumps('[e-mail]')

email = serializer.loads(token, max_age=3600)
print(email)

medium

A. Missing try-except block to handle expired or invalid tokens

B. Incorrect secret key used in serializer

C. Using dumps instead of loads to decode token

D. max_age parameter is not supported in loads

Solution

1. Step 1: Review the code for error handling

   The code calls loads without try-except, so expired or invalid tokens cause exceptions.

2. Step 2: Identify the missing safety measure

   Proper pattern uses try-except to catch exceptions and handle errors gracefully.

3. Final Answer:

   Missing try-except block to handle expired or invalid tokens -> Option A

4. Quick Check:

   Always catch exceptions when verifying tokens [OK]

Hint: Always wrap loads in try-except to catch errors [OK]

Common Mistakes:

• Not handling exceptions on token verification
• Confusing dumps and loads usage
• Assuming max_age is unsupported

5. You want to implement a password reset feature in Flask that sends a reset link with a token valid for 30 minutes. Which approach correctly combines token creation, expiration, and email sending?

hard

A. Store user password in token, send email with token, verify token by comparing passwords

B. Generate token with random string, send email with token, verify token by checking string length

C. Create a URLSafeTimedSerializer with secret key, generate token with dumps(user_email), send email with link containing token, verify token with loads(token, max_age=1800)

D. Create token with dumps(user_email), send email without token, verify token with loads(token, max_age=3600)

Solution

1. Step 1: Understand token creation and expiration

   Use URLSafeTimedSerializer with secret key to create a token from user email; set max_age to 1800 seconds (30 minutes) when verifying.

2. Step 2: Combine with email sending and verification

   Send the token in the reset link via email; verify token on reset page using loads with max_age to ensure expiration.

3. Final Answer:

   Create a URLSafeTimedSerializer with secret key, generate token with dumps(user_email), send email with link containing token, verify token with loads(token, max_age=1800) -> Option C

4. Quick Check:

   Serializer + dumps + max_age + email link = secure reset [OK]

Hint: Use serializer dumps and loads with max_age for timed tokens [OK]

Common Mistakes:

• Not setting max_age for token expiration
• Sending token without including it in email link
• Storing passwords in tokens