Why DRF authentication (Token, JWT) in Django? - Purpose & Use Cases

The Big Idea

Discover how DRF authentication saves you from messy, risky login code!

The Scenario

Imagine building a web app where users must log in to see their private data. You try to check their username and password on every page manually, passing credentials with every request.

The Problem

Manually handling user authentication is slow and risky. You might forget to check credentials on some pages, passwords could be exposed, and managing sessions becomes a tangled mess.

The Solution

DRF authentication with Token or JWT handles user identity securely and automatically. It lets your app verify users with simple tokens, so you don't have to manage passwords or sessions yourself.

Before vs After

✗ Before

if request.POST['username'] == stored_user and request.POST['password'] == stored_pass:
    show_private_data()

✓ After

authentication_classes = [TokenAuthentication]
# User sends token, DRF checks it automatically

What It Enables

It enables secure, scalable user authentication that works smoothly across web and mobile apps without exposing sensitive data.

Real Life Example

A mobile app where users log in once and get a token. Every time they open the app, the token lets them access their profile without re-entering passwords.

Key Takeaways

Manual authentication is error-prone and insecure.

DRF Token and JWT handle user identity safely and automatically.

This makes building secure apps easier and more reliable.

Practice

1. What is the main difference between TokenAuthentication and JWTAuthentication in Django REST Framework?

easy

A. TokenAuthentication uses simple tokens stored on the server; JWTAuthentication uses encoded tokens with expiry.

B. TokenAuthentication requires username and password every request; JWTAuthentication does not.

C. TokenAuthentication encrypts tokens; JWTAuthentication sends tokens as plain text.

D. TokenAuthentication is only for web apps; JWTAuthentication is only for mobile apps.

Solution

1. Step 1: Understand TokenAuthentication

   TokenAuthentication uses a simple token string stored on the server and sent by the client to identify the user.

2. Step 2: Understand JWTAuthentication

   JWTAuthentication uses JSON Web Tokens that are encoded, include expiry info, and do not require server storage.

3. Final Answer:

   TokenAuthentication uses simple tokens stored on the server; JWTAuthentication uses encoded tokens with expiry. -> Option A

4. Quick Check:

   Token vs JWT difference = D [OK]

Hint: Token is simple stored string; JWT is encoded with expiry [OK]

Common Mistakes:

• Thinking JWT tokens are stored on the server
• Confusing token encryption with encoding
• Assuming TokenAuthentication requires password every request

2. Which of the following is the correct way to add TokenAuthentication to a Django REST Framework view?

easy

A. authentication_classes = ["rest_framework.authentication.TokenAuthentication"]

B. authentication_classes = [TokenAuthentication]

C. authentication_classes = [rest_framework.authentication.TokenAuthentication]

D. authentication_classes = [TokenAuthentication()]

Solution

1. Step 1: Recall how to import and use authentication classes

   Authentication classes must be imported and instantiated, so use TokenAuthentication() not just the class name or string.

2. Step 2: Check syntax for authentication_classes

   It expects a list of authentication class instances, so the correct syntax is [TokenAuthentication()] with parentheses.

3. Final Answer:

   authentication_classes = [TokenAuthentication()] -> Option D

4. Quick Check:

   Use class instances in list = A [OK]

Hint: Use class instances with parentheses in authentication_classes list [OK]

Common Mistakes:

• Using strings instead of class instances
• Forgetting parentheses after class name
• Not importing TokenAuthentication before use

3. Given this Django REST Framework view snippet using JWTAuthentication, what will happen if the token is expired?

from rest_framework_simplejwt.authentication import JWTAuthentication
from rest_framework.views import APIView
from rest_framework.response import Response

class MyView(APIView):
    authentication_classes = [JWTAuthentication()]

    def get(self, request):
        return Response({"user": str(request.user)})

medium

A. The request will succeed but request.user will be None.

B. The request will succeed and return the user even if token expired.

C. The request will be denied with a 401 Unauthorized error.

D. The server will crash with an exception.

Solution

1. Step 1: Understand JWTAuthentication behavior on expired tokens

   JWTAuthentication checks token expiry and rejects requests with expired tokens by raising an authentication error.

2. Step 2: Effect on the APIView request

   When token is expired, the request is denied with a 401 Unauthorized response automatically by DRF.

3. Final Answer:

   The request will be denied with a 401 Unauthorized error. -> Option C

4. Quick Check:

   Expired JWT causes 401 error = B [OK]

Hint: Expired JWT tokens cause 401 Unauthorized error [OK]

Common Mistakes:

• Assuming expired token returns user as None
• Thinking expired token lets request pass
• Expecting server crash on expired token

4. You wrote this code to enable TokenAuthentication but your API always returns 403 Forbidden. What is the likely mistake?

from rest_framework.authentication import TokenAuthentication

class MyView(APIView):
    authentication_classes = [TokenAuthentication]

    def get(self, request):
        return Response({"message": "Hello"})

medium

A. Forgot to add parentheses after TokenAuthentication in authentication_classes.

B. TokenAuthentication is not imported correctly.

C. The get method should be named post.

D. authentication_classes should be a tuple, not a list.

Solution

1. Step 1: Check authentication_classes syntax

   authentication_classes must contain instances, so TokenAuthentication() with parentheses, not the class itself.

2. Step 2: Effect of missing parentheses

   Without parentheses, DRF does not recognize the authentication class properly, causing 403 Forbidden errors.

3. Final Answer:

   Forgot to add parentheses after TokenAuthentication in authentication_classes. -> Option A

4. Quick Check:

   Use TokenAuthentication() not TokenAuthentication = C [OK]

Hint: Always instantiate authentication classes with () [OK]

Common Mistakes:

• Using class name without parentheses
• Confusing 403 with 401 errors
• Changing method name unnecessarily

5. You want to protect an API endpoint so only users with a valid JWT token can access it, and you want tokens to expire after 5 minutes. Which settings and code changes should you apply?

hard

A. Set TOKEN_EXPIRE_TIME = 300 in settings and use TokenAuthentication() in authentication_classes.

B. Set SIMPLE_JWT['ACCESS_TOKEN_LIFETIME'] = timedelta(minutes=5) in settings and use JWTAuthentication() in authentication_classes.

C. Use JWTAuthentication() in authentication_classes and set JWT_EXPIRATION_DELTA = 5 in settings.

D. Use TokenAuthentication() and manually check token age in the view.

Solution

1. Step 1: Configure JWT token expiry

   In Django REST Framework Simple JWT, set ACCESS_TOKEN_LIFETIME to 5 minutes using timedelta in settings.

2. Step 2: Use JWTAuthentication in the view

   Set authentication_classes = [JWTAuthentication()] to enforce JWT token authentication on the endpoint.

3. Final Answer:

   Set SIMPLE_JWT['ACCESS_TOKEN_LIFETIME'] = timedelta(minutes=5) in settings and use JWTAuthentication() in authentication_classes. -> Option B

4. Quick Check:

   JWT expiry + JWTAuthentication = A [OK]

Hint: Set ACCESS_TOKEN_LIFETIME and use JWTAuthentication() [OK]

Common Mistakes:

• Using TokenAuthentication instead of JWTAuthentication
• Setting wrong expiry setting names
• Trying to manually check token expiry in views