Template-level authorization in Flask - Step-by-Step Execution

Concept Flow - Template-level authorization

User sends request

↓

Flask view checks user login

↓

Render template with user info

↓

Template evaluates user permissions

↓

Show authorized content

↓

Hide or show alternative content

↓

Send final HTML to browser

The flow shows how Flask sends user info to the template, which then decides what content to show based on user permissions.

Execution Sample

Flask

from flask import Flask, render_template, session
app = Flask(__name__)

@app.route('/')
def home():
    user = session.get('user')
    return render_template('home.html', user=user)

This Flask route sends the user info to the template, which can then show or hide parts based on authorization.

Execution Table

Step	Action	User in session	Template check	Content Shown
1	Request received	None	No user info	Show login link
2	User logs in	user={'role':'admin'}	Check if user.role == 'admin'	Show admin panel
3	Render template	user={'role':'admin'}	Check if user.role == 'admin'	Show admin panel
4	User logs in as guest	user={'role':'guest'}	Check if user.role == 'admin'	Hide admin panel, show guest content
5	Render template	user={'role':'guest'}	Check if user.role == 'admin'	Hide admin panel, show guest content
6	User logs out	None	No user info	Show login link

💡 Execution stops after rendering template with content based on user role or no user.

Variable Tracker

Variable	Start	After Step 2	After Step 4	After Step 6
user	None	{'role':'admin'}	{'role':'guest'}	None

Key Moments - 2 Insights

Why does the template need user info passed from the view?

Because the template uses the user info to decide what content to show, as seen in steps 2 and 4 where user roles affect content.

What happens if user info is missing in the template?

The template shows default content like a login link, as in steps 1 and 6 where user is None.

Visual Quiz - 3 Questions

Look at the execution table, what content is shown at step 4 when user role is 'guest'?

A Hide admin panel, show guest content

B Show login link

C Show admin panel

D Show nothing

💡 Hint

Check the 'Content Shown' column for step 4 in the execution table.

At which step does the user log out and no user info is available?

A Step 2

B Step 4

C Step 6

D Step 3

💡 Hint

Look at the 'User in session' column for when it becomes None again.

If the user role was changed to 'admin' at step 4, what would the template show?

A Show login link

B Show admin panel

C Hide admin panel, show guest content

D Show error message

💡 Hint

Refer to steps 2 and 3 where user role 'admin' shows admin panel.

Concept Snapshot

Template-level authorization in Flask:
- Pass user info from view to template
- Use template logic to check user role
- Show or hide content accordingly
- Default to guest or login view if no user
- Keeps UI responsive to user permissions

Full Transcript

Template-level authorization in Flask works by passing user information from the Flask view function to the HTML template. The template then uses simple checks to decide which parts of the page to show or hide based on the user's role or login status. For example, if the user is an admin, the template shows admin controls. If no user is logged in, it shows a login link. This approach helps keep the user interface dynamic and secure by controlling content visibility directly in the template.

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