Authentication middleware in Django - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What does this Django authentication middleware do?

Consider this Django middleware snippet that checks user authentication status. What will be the behavior when an unauthenticated user accesses a protected view?

Django

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

    def __call__(self, request):
        if not request.user.is_authenticated:
            from django.http import HttpResponseForbidden
            return HttpResponseForbidden('Access denied')
        response = self.get_response(request)
        return response

A The middleware redirects unauthenticated users to the login page automatically.

B The middleware blocks unauthenticated users by returning a 403 Forbidden response.

C The middleware allows all users to access the view without restriction.

D The middleware raises an exception if the user is not authenticated.

💡 Hint

Look at the response returned when the user is not authenticated.

The middleware checks if the user is authenticated. If not, it returns an HttpResponseForbidden, which sends a 403 status code blocking access.

📝 Syntax

intermediate

Identify the syntax error in this Django middleware snippet

Which option correctly fixes the syntax error in this middleware code?

Django

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

    def __call__(self, request):
        if not request.user.is_authenticated:
            from django.http import HttpResponseRedirect
            return HttpResponseRedirect('/login/')
        return self.get_response(request)

A Add a colon at the end of the if statement line.

B Indent the import statement one level less.

C Replace __call__ with process_request method.

D Remove the return statement inside the if block.

💡 Hint

Check the if statement syntax carefully.

The if statement is missing a colon at the end, which is required in Python syntax.

❓ state_output

advanced

What is the value of request.user after this middleware runs?

Given this middleware that modifies the request user attribute, what will be the value of request.user in the view after middleware processing?

Django

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

    def __call__(self, request):
        class FakeUser:
            is_authenticated = True
            username = 'guest'
        request.user = FakeUser()
        response = self.get_response(request)
        return response

A An object with is_authenticated True and username 'guest'.

B The original user object from the request.

C None, because request.user is deleted.

D A string 'guest' instead of a user object.

💡 Hint

Look at how request.user is assigned inside the middleware.

The middleware replaces request.user with a new FakeUser object having is_authenticated True and username 'guest'.

🔧 Debug

advanced

Why does this authentication middleware cause a server error?

This middleware is intended to block unauthenticated users but causes a server error. What is the cause?

Django

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

    def __call__(self, request):
        if not request.user.is_authenticated:
            return redirect('/login/')
        return self.get_response(request)

A request.user.is_authenticated is not a valid attribute.

B The middleware should use HttpResponseRedirect instead of redirect.

C Middleware must not return a response directly.

D The redirect function is not imported, causing a NameError.

💡 Hint

Check if all functions used are properly imported.

The redirect function is used but not imported from django.shortcuts, causing a NameError at runtime.

🧠 Conceptual

expert

Which statement best describes Django authentication middleware behavior?

Select the most accurate description of how Django's built-in AuthenticationMiddleware works.

A It encrypts user credentials on every request to enhance security.

B It automatically redirects unauthenticated users to the login page for all views.

C It attaches a user object to every request, representing the currently logged-in user or an anonymous user if not logged in.

D It replaces the session middleware and manages sessions internally.

💡 Hint

Think about what request.user contains after AuthenticationMiddleware runs.

AuthenticationMiddleware adds a user attribute to the request, which is either the logged-in user or an anonymous user object. It does not redirect or encrypt credentials.

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