Authentication middleware in Django - Mini Project: Build & Apply

Authentication middleware

📖 Scenario: You are building a Django web application that needs to check if a user is authenticated before allowing access to certain views. You will create a simple authentication middleware that checks if the user is logged in and redirects them if not.

🎯 Goal: Create a Django middleware class named SimpleAuthMiddleware that checks if the user is authenticated. If the user is not authenticated, redirect them to the login page. Otherwise, allow the request to continue.

📋 What You'll Learn

Create a middleware class named SimpleAuthMiddleware

Check if the user is authenticated using request.user.is_authenticated

Redirect unauthenticated users to /login/

Allow authenticated users to continue processing the request

Add the middleware to Django's MIDDLEWARE list

💡 Why This Matters

🌍 Real World

Authentication middleware is used in real web applications to protect pages and resources from unauthorized access, ensuring only logged-in users can see certain content.

💼 Career

Understanding how to write and configure middleware is important for backend developers working with Django to implement security and request processing logic.

1

Create the middleware class skeleton

Create a Python class named SimpleAuthMiddleware with an __init__ method that takes get_response as a parameter and stores it as an instance variable.

Django

class SimpleAuthMiddleware:
    def __init__(self, get_response):
        # Your code here

Hint

Remember, the middleware class needs an __init__ method that saves the get_response callable.

2

Add the __call__ method to process requests

Add a __call__ method to SimpleAuthMiddleware that takes request as a parameter and stores the result of calling self.get_response(request) in a variable named response.

Django

class SimpleAuthMiddleware:
    def __init__(self, get_response):
        self.get_response = get_response

    def __call__(self, request):
        # Your code here

Hint

The __call__ method must call self.get_response(request) and return the response.

3

Check if user is authenticated and redirect if not

Inside the __call__ method, before calling self.get_response(request), check if request.user.is_authenticated is False. If so, import HttpResponseRedirect from django.http and return HttpResponseRedirect('/login/'). Otherwise, continue to call self.get_response(request).

Django

from django.http import HttpResponseRedirect

class SimpleAuthMiddleware:
    def __init__(self, get_response):
        self.get_response = get_response

    def __call__(self, request):
        # Your code here

Hint

Use if not request.user.is_authenticated: to check authentication and return a redirect response.

4

Add the middleware to Django settings

In your Django settings.py file, add the string 'path.to.SimpleAuthMiddleware' to the MIDDLEWARE list. Replace path.to with the actual Python import path where SimpleAuthMiddleware is defined.

Django

# In settings.py
MIDDLEWARE = [
    # existing middleware entries
    # Your code here
]

Hint

Insert the middleware class path as a string inside the MIDDLEWARE list in settings.py.

Practice

1. What is the main purpose of Django's AuthenticationMiddleware?

easy

A. To serve static files like CSS and JavaScript

B. To handle database connections automatically

C. To attach the authenticated user to request.user on every request

D. To manage URL routing and view dispatching

Solution

1. Step 1: Understand middleware role

   AuthenticationMiddleware processes each request to identify the user making it.

2. Step 2: Check what it attaches to request

   It adds the user object to request.user so views can access user info easily.

3. Final Answer:

   To attach the authenticated user to request.user on every request -> Option C

4. Quick Check:

   AuthenticationMiddleware = attaches user info [OK]

Hint: AuthenticationMiddleware sets request.user for user info [OK]

Common Mistakes:

• Confusing it with static file handling middleware
• Thinking it manages database connections
• Assuming it handles URL routing

2. Which of the following is the correct way to add AuthenticationMiddleware in Django's settings.py?

easy

A. 'django.contrib.auth.middleware.AuthenticationMiddleware' must be listed after 'django.contrib.sessions.middleware.SessionMiddleware'

B. 'django.contrib.auth.middleware.AuthenticationMiddleware' must be listed before 'django.contrib.sessions.middleware.SessionMiddleware'

C. 'django.contrib.auth.middleware.AuthenticationMiddleware' can be anywhere in the list

D. 'django.contrib.auth.middleware.AuthenticationMiddleware' should be the first middleware in the list

Solution

1. Step 1: Recall middleware order importance

   SessionMiddleware must run before AuthenticationMiddleware because authentication depends on session data.

2. Step 2: Confirm correct order

   AuthenticationMiddleware should be listed after SessionMiddleware in the MIDDLEWARE list.

3. Final Answer:

   AuthenticationMiddleware must be listed after SessionMiddleware -> Option A

4. Quick Check:

   SessionMiddleware before AuthenticationMiddleware [OK]

Hint: AuthenticationMiddleware comes after SessionMiddleware in settings [OK]

Common Mistakes:

• Placing AuthenticationMiddleware before SessionMiddleware
• Ignoring middleware order importance
• Assuming order does not matter

3. Given this Django view code snippet, what will print(request.user.is_authenticated) output if the user is logged in?

medium

A. Raises AttributeError

B. False

C. None

D. True

Solution

1. Step 1: Understand request.user with AuthenticationMiddleware

   When AuthenticationMiddleware is enabled, request.user is a User object or AnonymousUser.

2. Step 2: Check is_authenticated property for logged-in user

   For logged-in users, request.user.is_authenticated returns True.

3. Final Answer:

   True -> Option D

4. Quick Check:

   Logged-in user means is_authenticated = True [OK]

Hint: request.user.is_authenticated is True if logged in [OK]

Common Mistakes:

• Expecting False for logged-in users
• Thinking it returns None
• Assuming it raises an error

4. You added AuthenticationMiddleware to your Django project but request.user is always AnonymousUser. What is the most likely cause?

medium

A. You forgot to add "django.contrib.sessions.middleware.SessionMiddleware" before AuthenticationMiddleware

B. You did not import AuthenticationMiddleware in your views.py

C. You need to restart the database server

D. You must add AuthenticationMiddleware to INSTALLED_APPS

Solution

1. Step 1: Understand dependency on session middleware

   AuthenticationMiddleware relies on session data to identify users, so SessionMiddleware must run first.

2. Step 2: Identify missing or misordered middleware

   If SessionMiddleware is missing or placed after AuthenticationMiddleware, user info won't load, causing AnonymousUser.

3. Final Answer:

   Forgot to add SessionMiddleware before AuthenticationMiddleware -> Option A

4. Quick Check:

   SessionMiddleware missing or misplaced causes AnonymousUser [OK]

Hint: SessionMiddleware must come before AuthenticationMiddleware [OK]

Common Mistakes:

• Thinking you must import middleware in views
• Restarting database unrelated to middleware
• Adding middleware to INSTALLED_APPS instead of MIDDLEWARE

5. You want to create a custom middleware that only allows authenticated users to access certain views. Which is the best way to use Django's AuthenticationMiddleware to achieve this?

hard

A. Use AuthenticationMiddleware only in views, not in middleware

B. Add AuthenticationMiddleware to MIDDLEWARE, then check request.user.is_authenticated in your custom middleware before view runs

C. Add AuthenticationMiddleware after your custom middleware in MIDDLEWARE list

D. Replace AuthenticationMiddleware with your custom middleware that handles authentication manually

Solution

1. Step 1: Use AuthenticationMiddleware to set request.user

   AuthenticationMiddleware must be in MIDDLEWARE to provide user info on requests.

2. Step 2: Implement custom middleware after AuthenticationMiddleware

   Your custom middleware can check request.user.is_authenticated to allow or block access before views run.

3. Final Answer:

   Add AuthenticationMiddleware to MIDDLEWARE, then check request.user.is_authenticated in your custom middleware before view runs -> Option B

4. Quick Check:

   AuthenticationMiddleware first, then custom auth check [OK]

Hint: Check request.user.is_authenticated in custom middleware after AuthenticationMiddleware [OK]

Common Mistakes:

• Replacing AuthenticationMiddleware instead of extending it
• Placing AuthenticationMiddleware after custom middleware
• Trying to use AuthenticationMiddleware only inside views