Permission checking in routes in Flask - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when a user without permission accesses this Flask route?

Consider this Flask route that checks user permissions before allowing access:

from flask import Flask, abort
app = Flask(__name__)

@app.route('/admin')
def admin_panel():
    user = get_current_user()
    if not user.has_permission('admin'):
        abort(403)
    return 'Welcome to admin panel'

What will the user see if they do not have the 'admin' permission?

Flask

from flask import Flask, abort
app = Flask(__name__)

@app.route('/admin')
def admin_panel():
    user = get_current_user()
    if not user.has_permission('admin'):
        abort(403)
    return 'Welcome to admin panel'

A The server crashes with an exception.

B The user sees a 403 Forbidden error page.

C The user is redirected to the login page.

D The user sees the message 'Welcome to admin panel'.

💡 Hint

Think about what abort(403) does in Flask.

The abort(403) function immediately stops the request and returns a 403 Forbidden HTTP error to the user. This means the user will see a 403 error page if they lack the required permission.

📝 Syntax

intermediate

Identify the syntax error in this Flask permission check

Look at this Flask route code snippet:

@app.route('/dashboard')
def dashboard():
    user = get_current_user()
    if user.has_permission('view_dashboard')
        return 'Dashboard content'
    else:
        abort(403)

What is the syntax error here?

Flask

@app.route('/dashboard')
def dashboard():
    user = get_current_user()
    if user.has_permission('view_dashboard')
        return 'Dashboard content'
    else:
        abort(403)

A Missing colon ':' after the if condition.

B Missing parentheses in abort call.

C Indentation error in the else block.

D Route decorator is missing parentheses.

💡 Hint

Check the syntax of the if statement line.

In Python, an if statement must end with a colon ':'. The line if user.has_permission('view_dashboard') is missing this colon, causing a syntax error.

❓ state_output

advanced

What is the response status code when permission check passes?

Given this Flask route:

@app.route('/settings')
def settings():
    user = get_current_user()
    if user.has_permission('edit_settings'):
        return 'Settings page', 200
    else:
        abort(403)

What HTTP status code will the client receive if the user has the 'edit_settings' permission?

Flask

@app.route('/settings')
def settings():
    user = get_current_user()
    if user.has_permission('edit_settings'):
        return 'Settings page', 200
    else:
        abort(403)

A 500

B 404

C 403

D 200

💡 Hint

Look at the return statement when permission is granted.

The route returns the string 'Settings page' with status code 200 when the user has permission. So the client receives HTTP 200 OK.

🔧 Debug

advanced

Why does this permission check always allow access?

Examine this Flask route:

@app.route('/profile')
def profile():
    user = get_current_user()
    if user.has_permission('view_profile') == False:
        return 'Access denied', 403
    return 'User profile'

Users report they can access the profile page even without permission. Why?

Flask

@app.route('/profile')
def profile():
    user = get_current_user()
    if user.has_permission('view_profile') == False:
        return 'Access denied', 403
    return 'User profile'

A The permission check uses '== False' which may fail if has_permission returns None or other falsy values.

B The function get_current_user() is not defined, so user is None.

C The route decorator is missing parentheses.

D The return statement for access denied is missing abort() call.

💡 Hint

Consider how Python evaluates boolean expressions and the return value of has_permission.

If has_permission returns a falsy value other than exactly False (like None), the condition user.has_permission('view_profile') == False will be False, allowing access incorrectly. It's safer to use if not user.has_permission(...).

🧠 Conceptual

expert

Which approach best secures multiple routes with the same permission check?

You want to protect several Flask routes so only users with 'editor' permission can access them. Which approach is best to avoid repeating permission checks in every route?

A Check permissions only in the first route and assume users have permission for others.

B Manually add the permission check code inside each route function.

C Create a custom decorator that checks 'editor' permission and apply it to all relevant routes.

D Use a global before_request function that aborts if the user lacks 'editor' permission for all routes.

💡 Hint

Think about code reuse and clear permission enforcement per route.

A custom decorator lets you write the permission check once and reuse it on any route needing that permission. This keeps code clean and consistent. Using before_request globally may block unrelated routes. Manual checks cause repetition. Assuming permissions is insecure.