Why authorization matters in Django - Visual Breakdown

Concept Flow - Why authorization matters

User sends request

↓

Authentication: Who is user?

↓

Authorization: What can user do?

↓

Allowed

↓

Access granted

↓

Response sent

The flow shows how a user request is first checked for identity (authentication), then checked for permissions (authorization), leading to access granted or denied.

Execution Sample

Django

from django.shortcuts import redirect
from django.http import HttpResponse

def view(request):
    if not request.user.is_authenticated:
        return redirect('login')
    if not request.user.has_perm('app.view_data'):
        return HttpResponse('Access denied')
    return HttpResponse('Data shown')

This Django view checks if the user is logged in and has permission before showing data.

Execution Table

Step	Check	Condition	Result	Action
1	Is user authenticated?	False	No	Redirect to login page
2	Is user authenticated?	True	Yes	Check permission
3	Does user have 'app.view_data' permission?	False	No	Return 'Access denied' response
4	Does user have 'app.view_data' permission?	True	Yes	Return 'Data shown' response

💡 Execution stops when user is either redirected or response is returned based on authentication and authorization checks.

Variable Tracker

Variable	Start	After Step 1	After Step 3	Final
request.user.is_authenticated	Unknown	False or True	True if passed step 1	True if passed step 3
request.user.has_perm('app.view_data')	Unknown	Not checked	False or True	True if passed step 3

Key Moments - 2 Insights

Why do we check authentication before authorization?

Because authorization depends on knowing who the user is. The execution_table shows authentication checked first at step 1 before permission check at step 3.

What happens if a user is not authorized?

The code returns an 'Access denied' response as shown in step 3 of the execution_table, stopping further access.

Visual Quiz - 3 Questions

Look at the execution_table, what happens if request.user.is_authenticated is False?

A User gets 'Access denied' message

B User is redirected to login page

C User is shown data

D Nothing happens

💡 Hint

See step 1 in execution_table where authentication is False

At which step does the code check if the user has permission 'app.view_data'?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Check the 'Check' column in execution_table for permission check

If the user is authenticated but lacks permission, what is the final action?

A Redirect to login

B Return 'Data shown' response

C Return 'Access denied' response

D Raise an error

💡 Hint

See step 3 in execution_table where permission is False

Concept Snapshot

Authorization controls what an authenticated user can do.
Always check authentication first, then authorization.
Deny access if permission is missing.
Protects sensitive data and actions.
In Django, use user.has_perm() to check permissions.

Full Transcript

This visual execution shows why authorization matters in Django. When a user sends a request, the system first checks if the user is authenticated, meaning logged in. If not, the user is redirected to the login page. If authenticated, the system then checks if the user has the required permission to view data. If the user lacks permission, access is denied with a message. Only if both checks pass does the system show the data. This flow protects resources by ensuring only allowed users can access them. The execution table traces these checks step-by-step, and the variable tracker shows how user authentication and permission states change during execution.

Practice

1. Why is authorization important in a Django web application?

easy

A. It helps in designing the user interface.

B. It speeds up the loading time of the website.

C. It automatically fixes bugs in the code.

D. It controls which users can access certain parts of the app.

Solution

1. Step 1: Understand the role of authorization

   Authorization decides what parts of the app a user can see or use.

2. Step 2: Compare with other options

   Speed, design, and bug fixing are unrelated to authorization.

3. Final Answer:

   It controls which users can access certain parts of the app. -> Option D

4. Quick Check:

   Authorization controls access = C [OK]

Hint: Authorization controls access, not speed or design [OK]

Common Mistakes:

• Confusing authorization with authentication
• Thinking authorization improves performance
• Believing authorization designs UI

2. Which Django decorator is used to require a user to be logged in before accessing a view?

easy

A. @permission_required

B. @login_required

C. @csrf_protect

D. @require_GET

Solution

1. Step 1: Identify the decorator for login requirement

   The decorator @login_required ensures only logged-in users access the view.

2. Step 2: Differentiate from other decorators

   @permission_required checks permissions, @csrf_protect protects against CSRF, and @require_GET limits HTTP methods.

3. Final Answer:

   @login_required -> Option B

4. Quick Check:

   Login check decorator = @login_required [OK]

Hint: Login check uses @login_required decorator [OK]

Common Mistakes:

• Using @permission_required instead of @login_required
• Confusing CSRF protection with authorization
• Mixing HTTP method decorators with authorization

3. Consider this Django view code:

@login_required
def dashboard(request):
    if not request.user.has_perm('app.view_dashboard'):
        return HttpResponse('Access Denied')
    return HttpResponse('Welcome to Dashboard')

What will a logged-in user without the 'app.view_dashboard' permission see?

medium

A. Access Denied

B. Welcome to Dashboard

C. A 404 Not Found error

D. A login page

Solution

1. Step 1: Analyze the permission check

   The code checks if the user has 'app.view_dashboard' permission; if not, it returns 'Access Denied'.

2. Step 2: Consider the user's permission

   The user is logged in but lacks the permission, so the 'Access Denied' response is returned.

3. Final Answer:

   Access Denied -> Option A

4. Quick Check:

   Permission missing shows 'Access Denied' = A [OK]

Hint: No permission means 'Access Denied' message shown [OK]

Common Mistakes:

• Assuming login means full access
• Thinking missing permission causes 404 error
• Confusing permission denial with login redirect

4. What is wrong with this Django view code for enforcing authorization?

def profile(request):
    if not request.user.is_authenticated:
        return HttpResponse('Please log in')
    if not request.user.has_perm('app.view_profile'):
        return HttpResponse('Access Denied')
    return HttpResponse('User Profile')

medium

A. It should use @login_required decorator instead of manual check.

B. The permission check is missing.

C. It returns the wrong HTTP status codes.

D. It does not check if the user is a superuser.

Solution

1. Step 1: Review authentication check method

   The code manually checks if the user is authenticated instead of using the standard @login_required decorator.

2. Step 2: Understand best practice

   Using @login_required is cleaner and automatically redirects unauthenticated users to login.

3. Final Answer:

   It should use @login_required decorator instead of manual check. -> Option A

4. Quick Check:

   Use @login_required for authentication checks [OK]

Hint: Use @login_required decorator, not manual authentication checks [OK]

Common Mistakes:

• Ignoring @login_required decorator
• Assuming manual checks are better
• Missing permission checks

5. You want to restrict access to a Django view so only users with both 'app.view_reports' permission and who are staff can access it. Which code snippet correctly enforces this?

hard

A. @login_required
def reports(request):
if not request.user.has_perm('app.view_reports'):
return HttpResponse('Access Denied')
return HttpResponse('Reports Page')

B. @login_required
def reports(request):
if request.user.is_staff or request.user.has_perm('app.view_reports'):
return HttpResponse('Reports Page')
return HttpResponse('Access Denied')

C. @permission_required('app.view_reports')
def reports(request):
if not request.user.is_staff:
return HttpResponse('Access Denied')
return HttpResponse('Reports Page')

D. @permission_required('app.view_reports')
@superuser_required
def reports(request):
return HttpResponse('Reports Page')

Solution

1. Step 1: Understand the permission and staff checks

   The view must check both permission and staff status before allowing access.

2. Step 2: Analyze each option

   @permission_required('app.view_reports') def reports(request): if not request.user.is_staff: return HttpResponse('Access Denied') return HttpResponse('Reports Page') uses @permission_required to check permission and then manually checks is_staff, denying access if false. This correctly enforces both conditions.

3. Step 3: Why other options fail

   @login_required def reports(request): if not request.user.has_perm('app.view_reports'): return HttpResponse('Access Denied') return HttpResponse('Reports Page') only checks permission but misses staff check; @login_required def reports(request): if request.user.is_staff or request.user.has_perm('app.view_reports'): return HttpResponse('Reports Page') return HttpResponse('Access Denied') uses OR instead of AND; @permission_required('app.view_reports') @superuser_required def reports(request): return HttpResponse('Reports Page') uses @superuser_required which is not a standard Django decorator and will cause a NameError.

4. Final Answer:

   @permission_required('app.view_reports') def reports(request): if not request.user.is_staff: return HttpResponse('Access Denied') return HttpResponse('Reports Page') -> Option C

5. Quick Check:

   @permission_required('app.view_reports') def reports(request): if not request.user.is_staff: return HttpResponse('Access Denied') return HttpResponse('Reports Page') [OK]

Hint: Use @permission_required plus manual staff check for AND condition [OK]

Common Mistakes:

• Using OR instead of AND for permission and staff
• Missing login or permission decorators
• Using non-standard decorators without import