Template-level authorization in Flask - Mini Project: Build & Apply

Template-level Authorization in Flask

📖 Scenario: You are building a simple Flask web app where users have different roles. Some parts of the page should only be visible to users with the 'admin' role.

🎯 Goal: Create a Flask app with a user dictionary, a role configuration, and a template that shows a special message only if the user is an admin.

📋 What You'll Learn

Create a dictionary called users with usernames and their roles

Create a variable called current_user set to a specific username

Use a Flask template with a conditional to show content only if current_user has the 'admin' role

Render the template in a Flask route

💡 Why This Matters

🌍 Real World

Many web apps show or hide parts of pages based on user roles, like admin panels or special buttons.

💼 Career

Understanding template-level authorization is key for building secure and user-friendly web applications.

1

Create the user roles dictionary

Create a dictionary called users with these exact entries: 'alice': 'admin', 'bob': 'user', 'carol': 'user'.

Flask

# Create the users dictionary with roles
# Your code here

Hint

Use curly braces to create the dictionary and colons to assign roles.

2

Set the current user

Create a variable called current_user and set it to the string 'alice'.

Flask

users = {'alice': 'admin', 'bob': 'user', 'carol': 'user'}
# Set the current_user variable
# Your code here

Hint

Assign the string 'alice' to the variable current_user.

3

Create the Flask app and template with authorization check

Import Flask and create an app. Define a route / that renders a template called index.html. Pass current_user and users to the template. In the template, use a Jinja2 {% if %} statement to show the text Welcome, admin! only if the role of current_user in users is 'admin'.

Flask

from flask import Flask, render_template

app = Flask(__name__)

# Define the route and render the template
# Your code here

Hint

Use @app.route('/') to create the home route and render_template to send variables to the template.

4

Add the template code for conditional display

Create a file called templates/index.html. Inside, write HTML that uses Jinja2 syntax. Add a conditional {% if users[current_user] == 'admin' %} that shows <p>Welcome, admin!</p> only if the current user is an admin. Otherwise, show <p>Welcome, user!</p>.

Flask

Hint

Use Jinja2 {% if %} and {% else %} tags to show different messages.

Practice

1. What is the main purpose of using template-level authorization in a Flask application?

easy

A. To control what content users can see based on their roles or permissions

B. To speed up the loading time of templates

C. To change the style of the webpage dynamically

D. To store user data securely in the database

Solution

1. Step 1: Understand template-level authorization

   Template-level authorization is about controlling visibility of content in templates based on user roles or permissions.

2. Step 2: Identify the main purpose

   The main goal is to restrict or allow content display depending on who the user is.

3. Final Answer:

   To control what content users can see based on their roles or permissions -> Option A

4. Quick Check:

   Authorization controls content visibility [OK]

Hint: Authorization controls content visibility in templates [OK]

Common Mistakes:

• Confusing authorization with styling or performance
• Thinking it stores data instead of controlling view
• Mixing backend data storage with frontend display control

2. Which of the following is the correct way to check a user's role in a Flask Jinja2 template?

easy

A. {{ if user.role == 'admin' }} ... {{ endif }}

B. {% check user.role == 'admin' %} ... {% endcheck %}

C. {% if user.role == 'admin' %} ... {% endif %}

D. <% if user.role == 'admin' %> ... <% endif %>

Solution

1. Step 1: Recall Jinja2 syntax for conditionals

   Jinja2 uses {% if condition %} ... {% endif %} blocks for conditional rendering.

2. Step 2: Match syntax with options

   {% if user.role == 'admin' %} ... {% endif %} uses correct Jinja2 syntax. The other options use invalid or other template syntax.

3. Final Answer:

   {% if user.role == 'admin' %} ... {% endif %} -> Option C

4. Quick Check:

   Jinja2 uses {% if %} ... {% endif %} [OK]

Hint: Use {% if %} ... {% endif %} for conditions in Jinja2 templates [OK]

Common Mistakes:

• Using {{ }} for control flow instead of {% %}
• Confusing Jinja2 with other template languages
• Using incorrect tags like <% %> which are not Jinja2

3. Given this Flask template snippet:

{% if user.is_authenticated and user.role == 'editor' %}
  
Edit content here
{% else %}
  
View only
{% endif %}

What will be displayed if user.is_authenticated is True but user.role is 'viewer'?

medium

A. Edit content here

B. View only

C. Nothing will be displayed

D. Template error occurs

Solution

1. Step 1: Evaluate the condition

   The condition requires user.is_authenticated to be True AND user.role to be 'editor'. Here, role is 'viewer', so condition is False.

2. Step 2: Determine which block runs

   Since condition is False, the else block runs, displaying <p>View only</p>.

3. Final Answer:

   <p>View only</p> -> Option B

4. Quick Check:

   Condition false triggers else block [OK]

Hint: Check both conditions; else block shows if any fail [OK]

Common Mistakes:

• Assuming only one condition matters
• Thinking 'viewer' role passes the 'editor' check
• Expecting no output when else block exists

4. You have this template code:

{% if user.role = 'admin' %}
  
Admin panel
{% endif %}

What is the problem with this code?

medium

A. Using <p> tags inside a template is not allowed

B. Missing else block for non-admin users

C. Incorrect indentation inside the if block

D. Using single equals sign (=) instead of double equals (==) in the if condition

Solution

1. Step 1: Identify the conditional syntax error

   In Jinja2, comparisons use '==' not '='. '=' is assignment and invalid in if conditions.

2. Step 2: Understand the impact

   Using '=' causes a template syntax error and prevents rendering.

3. Final Answer:

   Using single equals sign (=) instead of double equals (==) in the if condition -> Option D

4. Quick Check:

   Use '==' for comparisons in Jinja2 if statements [OK]

Hint: Use '==' for comparisons, '=' causes errors [OK]

Common Mistakes:

• Using '=' instead of '==' in conditions
• Thinking missing else causes syntax error
• Believing HTML tags are disallowed in templates

5. You want to show a special admin menu only if the user is authenticated and has either 'admin' or 'superuser' role. Which template code correctly implements this?

hard

A. {% if user.is_authenticated and user.role in ['admin', 'superuser'] %}
Admin Menu
{% endif %}

B. {% if user.is_authenticated or user.role == 'admin' or user.role == 'superuser' %}
Admin Menu
{% endif %}

C. {% if user.is_authenticated and user.role == 'admin' or 'superuser' %}
Admin Menu
{% endif %}

D. {% if user.is_authenticated and user.role == 'admin' or user.role == 'superuser' %}
Admin Menu
{% endif %}

Solution

1. Step 1: Understand the condition requirements

   User must be authenticated AND have role 'admin' OR 'superuser'.

2. Step 2: Analyze each option

   {% if user.is_authenticated and user.role == 'admin' or user.role == 'superuser' %}
   Admin Menu
   {% endif %} lacks parentheses around the or conditions, resulting in incorrect logic: (is_authenticated and role=='admin') or role=='superuser' due to operator precedence. {% if user.is_authenticated or user.role == 'admin' or user.role == 'superuser' %}
   Admin Menu
   {% endif %} uses or between authentication and roles, allowing unauthenticated users. {% if user.is_authenticated and user.role == 'admin' or 'superuser' %}
   Admin Menu
   {% endif %} has incorrect syntax and logic. {% if user.is_authenticated and user.role in ['admin', 'superuser'] %} <nav>Admin Menu</nav> {% endif %} uses 'in' to check role membership, which is clean and correct.

3. Final Answer:

   {% if user.is_authenticated and user.role in ['admin', 'superuser'] %} <nav>Admin Menu</nav> {% endif %} -> Option A

4. Quick Check:

   Use 'in' for multiple role checks with and for authentication [OK]

Hint: Use 'and' plus 'in' to check multiple roles cleanly [OK]

Common Mistakes:

• Using 'or' instead of 'and' for authentication
• Incorrect syntax for multiple role checks
• Missing parentheses causing logic errors