JWT token verification in FastAPI - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a JWT token in the context of FastAPI?

A JWT (JSON Web Token) is a compact, URL-safe token used to securely transmit information between parties. In FastAPI, it is commonly used to verify user identity and permissions without storing session data on the server.

beginner

What are the main parts of a JWT token?

A JWT token has three parts separated by dots: Header (describes the token type and algorithm), Payload (contains the claims or data), and Signature (verifies the token's integrity).

intermediate

How does FastAPI verify a JWT token?

FastAPI verifies a JWT token by decoding it using a secret key and checking the signature. It also validates claims like expiration time to ensure the token is still valid.

intermediate

What FastAPI dependency is commonly used to extract and verify JWT tokens from requests?

The OAuth2PasswordBearer dependency is often used to extract the token from the Authorization header, which can then be verified using JWT decoding functions.

beginner

Why is it important to check the token's expiration during JWT verification?

Checking the token's expiration ensures that old or stolen tokens cannot be used indefinitely, improving security by limiting how long a token is valid.

Which part of a JWT token contains the user's data or claims?

A Payload

B Header

C Signature

D Secret key

The Payload part contains the claims or user data.

In FastAPI, which header usually carries the JWT token for verification?

A Content-Type

B Authorization

C Accept

D User-Agent

The Authorization header carries the JWT token, typically as a Bearer token.

What happens if a JWT token's signature does not match during verification?

A The token is accepted

B The token is refreshed automatically

C The token is rejected as invalid

D The token is ignored

A mismatched signature means the token is invalid and should be rejected.

Which FastAPI tool helps to extract the JWT token from the request header?

A OAuth2PasswordBearer

B Depends

C Request

D Response

OAuth2PasswordBearer is used to extract the token from the Authorization header.

Why should you keep the secret key used for signing JWT tokens safe?

A To allow anyone to create tokens

B To make tokens expire faster

C To speed up token verification

D To prevent unauthorized token creation and verification

The secret key must be kept safe to prevent attackers from creating or verifying tokens.

Explain the process of verifying a JWT token in FastAPI from receiving the token to validating it.

Think about how FastAPI gets the token and what checks it does to trust it.

Describe why JWT tokens are useful for stateless authentication in web applications.

Consider how JWT helps servers avoid keeping user sessions.

Practice

1. What is the main purpose of JWT token verification in a FastAPI application?

easy

A. To check if the user token is valid and trusted

B. To encrypt the user's password

C. To store user data in the database

D. To generate HTML pages dynamically

Solution

1. Step 1: Understand JWT token role

   JWT tokens are used to prove a user's identity securely.

2. Step 2: Identify verification purpose

   Verification checks if the token is valid and trusted before allowing access.

3. Final Answer:

   To check if the user token is valid and trusted -> Option A

4. Quick Check:

   JWT verification = check token validity [OK]

Hint: JWT verification means confirming token is valid [OK]

Common Mistakes:

• Confusing verification with encryption
• Thinking JWT stores user data permanently
• Mixing token verification with UI rendering

2. Which FastAPI dependency is commonly used to extract and verify a JWT token from the request header?

easy

A. Depends()

B. Form()

C. RequestBody()

D. OAuth2PasswordBearer

Solution

1. Step 1: Identify FastAPI dependency for JWT

   OAuth2PasswordBearer is designed to extract bearer tokens from headers.

2. Step 2: Confirm usage for JWT verification

   This dependency helps get the token string to verify it in your code.

3. Final Answer:

   OAuth2PasswordBearer -> Option D

4. Quick Check:

   OAuth2PasswordBearer extracts JWT token [OK]

Hint: OAuth2PasswordBearer extracts token from header [OK]

Common Mistakes:

• Using Depends() alone without OAuth2PasswordBearer
• Confusing Form() with header token extraction
• Using RequestBody() which reads body, not headers

3. Given this FastAPI code snippet, what will happen if the JWT token is invalid?

async def get_current_user(token: str = Depends(oauth2_scheme)):
    try:
        payload = jwt.decode(token, SECRET_KEY, algorithms=[ALGORITHM])
    except JWTError:
        raise HTTPException(status_code=401, detail="Invalid token")
    return payload

medium

A. The function returns the payload even if token is invalid

B. The server crashes with an unhandled exception

C. An HTTP 401 error is raised with 'Invalid token' message

D. The token is ignored and user is treated as anonymous

Solution

1. Step 1: Analyze try-except block

   If jwt.decode fails, it raises JWTError which is caught by except.

2. Step 2: Check except block behavior

   It raises HTTPException with status 401 and message 'Invalid token'.

3. Final Answer:

   An HTTP 401 error is raised with 'Invalid token' message -> Option C

4. Quick Check:

   Invalid token triggers HTTP 401 error [OK]

Hint: Invalid JWT triggers HTTPException 401 [OK]

Common Mistakes:

• Assuming function returns payload on invalid token
• Thinking server crashes without handling error
• Believing token is ignored silently

4. Identify the error in this FastAPI JWT verification code:

from fastapi import Depends, HTTPException
from jose import jwt, JWTError

def verify_token(token: str):
    try:
        payload = jwt.decode(token, SECRET_KEY, algorithms=[ALGORITHM])
    except:
        HTTPException(status_code=401, detail="Invalid token")
    return payload

medium

A. HTTPException is raised but not returned or raised properly

B. Missing import for HTTPException

C. jwt.decode is called with wrong parameters

D. The function should not return payload

Solution

1. Step 1: Check exception handling

   HTTPException is created but not raised or returned, so error is ignored.

2. Step 2: Correct usage of HTTPException

   Must use 'raise HTTPException(...)' to properly stop execution and send error.

3. Final Answer:

   HTTPException is raised but not returned or raised properly -> Option A

4. Quick Check:

   Use 'raise' keyword with HTTPException [OK]

Hint: Always 'raise' HTTPException to trigger error [OK]

Common Mistakes:

• Forgetting 'raise' before HTTPException
• Catching too broad exceptions without logging
• Returning payload even on error

5. How can you protect a FastAPI route so that only requests with a valid JWT token can access it?

hard

A. Check the token manually inside the route function without dependencies

B. Use a dependency that verifies the JWT token and include it in the route

C. Add a middleware that ignores JWT tokens

D. Use a global variable to store token validity

Solution

1. Step 1: Understand FastAPI dependencies

   Dependencies can run code before route logic and reject invalid requests.

2. Step 2: Use dependency to verify JWT

   Including a JWT verification dependency ensures only valid tokens allow access.

3. Final Answer:

   Use a dependency that verifies the JWT token and include it in the route -> Option B

4. Quick Check:

   Dependency verifies JWT before route runs [OK]

Hint: Protect routes with JWT verification dependency [OK]

Common Mistakes:

• Checking token inside route instead of dependency
• Ignoring token verification in middleware
• Using global variables for token state