JWT token verification in FastAPI - Step-by-Step Execution

Concept Flow - JWT token verification

Receive HTTP request with JWT token

↓

Extract token from Authorization header

↓

Decode token using secret key

↓

Check token signature validity

↓

Check token expiry

↓

If expired?

↓

Reject

↓

Return response

This flow shows how a JWT token is extracted, decoded, verified for signature and expiry, then either accepted or rejected.

Execution Sample

FastAPI

from fastapi import FastAPI, Depends, HTTPException
from fastapi.security import HTTPBearer
import jwt

app = FastAPI()
security = HTTPBearer()

Setup FastAPI app and HTTPBearer security to extract JWT token from requests.

Execution Table

Step	Action	Input	Result	Next Step
1	Receive HTTP request	Authorization: Bearer <token>	Token extracted	Decode token
2	Decode token	<token>	Payload or error	Check signature validity
3	Check signature	Decoded payload	Valid or invalid	If invalid reject, else check expiry
4	Check expiry	Payload 'exp' field	Expired or valid	If expired reject, else allow
5	Allow access	Valid token	User info returned	Process request
6	Reject request	Invalid or expired token	HTTP 401 Unauthorized	End

💡 Execution stops when token is either accepted (valid and not expired) or rejected (invalid signature or expired)

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
token	None	<token string>	<decoded payload or error>	<valid or invalid>	<expired or valid>	Valid token or rejection
payload	None	None	{user_id, exp, ...}	{user_id, exp, ...}	{user_id, exp, ...}	User info or None

Key Moments - 3 Insights

Why do we check the token signature before expiry?

Because if the signature is invalid (see step 3 in execution_table), the token is tampered and should be rejected immediately without checking expiry.

What happens if the token is expired?

At step 4, if the 'exp' field shows the token is expired, the request is rejected with HTTP 401 Unauthorized (step 6).

Where do we get the token from in the HTTP request?

At step 1, the token is extracted from the Authorization header using HTTPBearer security scheme.

Visual Quiz - 3 Questions

Look at the execution_table, what happens at step 3 if the token signature is invalid?

A The token is rejected and request ends

B The token is accepted and request proceeds

C The expiry is checked next

D The token is decoded again

💡 Hint

Refer to step 3 in execution_table where invalid signature leads to rejection

At which step does the system check if the token is expired?

A Step 1

B Step 4

C Step 2

D Step 6

💡 Hint

Check execution_table row for step 4 about expiry check

If the token is valid and not expired, what is the final action?

A Reject request with 401

B Decode token again

C Return user info and allow access

D Extract token from header

💡 Hint

Look at step 5 in execution_table for valid token outcome

Concept Snapshot

JWT token verification in FastAPI:
- Extract token from Authorization header
- Decode token using secret key
- Verify signature validity
- Check token expiry
- Accept if valid and not expired
- Reject with 401 if invalid or expired

Full Transcript

This visual execution trace shows how FastAPI verifies a JWT token. First, the token is extracted from the Authorization header using HTTPBearer. Then the token is decoded using a secret key. The signature is checked to ensure the token is not tampered. If the signature is invalid, the request is rejected immediately. If valid, the token expiry time is checked. If expired, the request is rejected. If not expired, the user info from the token is returned and access is allowed. This step-by-step process ensures secure access control using JWT tokens.