Session security considerations in Django - Step-by-Step Execution

Concept Flow - Session security considerations

User logs in

↓

Server creates session ID

↓

Session ID sent to user as cookie

↓

User sends requests with session cookie

↓

Server validates session ID

↓

Access granted or denied

↓

Session expires or user logs out

This flow shows how a session is created, sent, validated, and eventually ended to keep user data secure.

Execution Sample

Django

def login(request):
    user = authenticate_user(request)
    if user:
        request.session['user_id'] = user.id
        request.session.set_expiry(300)  # 5 minutes
        return redirect('home')

This code logs in a user, creates a session with a user ID, and sets the session to expire after 5 minutes.

Execution Table

Step	Action	Session State	Security Check	Result
1	User submits login form	No session	N/A	Authenticate user
2	User authenticated	Create session with user_id	Set session expiry to 300s	Session cookie sent
3	User sends request with session cookie	Session with user_id active	Check session expiry and validity	Access granted
4	User inactive for 5 minutes	Session expired	Session expiry check fails	Access denied, redirect to login
5	User logs out	Session cleared	Session invalidated	User logged out

💡 Session expires after timeout or user logs out, stopping access.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
session['user_id']	None	user.id	user.id	None	None
session expiry	None	300 seconds	300 seconds	Expired	None
session cookie	None	Sent to user	Sent with requests	Expired/Removed	Removed

Key Moments - 3 Insights

Why do we set a session expiry time?

Setting a session expiry limits how long a session stays valid, reducing risk if a session cookie is stolen. See execution_table step 2 and 4 where expiry is set and checked.

What happens if the session cookie is stolen?

If stolen, the attacker can impersonate the user until the session expires or is invalidated. Using HTTPS and HttpOnly cookies helps protect the cookie. This is implied in the session cookie handling in steps 2 and 3.

Why clear the session on logout?

Clearing the session removes all stored data and invalidates the session cookie, preventing reuse. See execution_table step 5 where session is cleared and user logged out.

Visual Quiz - 3 Questions

Look at the execution_table, what is the session state after step 3?

A Session with user_id active

B Session expired

C No session

D Session cleared

💡 Hint

Check the 'Session State' column for step 3 in the execution_table.

At which step does the session expiry cause access to be denied?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look at the 'Security Check' and 'Result' columns in the execution_table for when expiry fails.

If we remove the session expiry setting, what would change in the execution_table?

A Step 2 would fail to create a session

B Step 4 would not expire the session

C Step 5 would not clear the session

D Step 3 would deny access

💡 Hint

Refer to the 'Session expiry' variable in variable_tracker and step 4 in execution_table.

Concept Snapshot

Session security in Django:
- Server creates a session ID after login
- Session ID stored in secure cookie
- Set session expiry to limit lifetime
- Validate session on each request
- Clear session on logout to prevent reuse

Full Transcript

This visual execution shows how Django manages session security. When a user logs in, the server creates a session with a unique ID and stores the user ID in it. This session ID is sent to the user as a cookie. Each time the user makes a request, the server checks if the session is valid and not expired. Sessions have expiry times to reduce risk if cookies are stolen. When the user logs out or the session expires, the session data is cleared and access is denied. This process helps keep user data safe during web interactions.