OAuth2 password flow in FastAPI - Step-by-Step Execution

Concept Flow - OAuth2 password flow

User enters username & password

↓

Client sends POST request to /token

↓

Server verifies credentials

↓

Generate access [Return error

User sends username and password to server, server checks them, then returns an access token if valid.

Execution Sample

FastAPI

from fastapi import FastAPI, Depends
from fastapi.security import OAuth2PasswordRequestForm

app = FastAPI()

@app.post('/token')
async def login(form_data: OAuth2PasswordRequestForm = Depends()):
    # verify and return token

This code handles the POST request to /token, verifies user credentials, and returns an access token.

Execution Table

Step	Action	Input	Check	Result	Output
1	Receive POST /token	username='alice', password='secret'	None	Request accepted	None
2	Extract credentials	username='alice', password='secret'	None	Credentials extracted	None
3	Verify credentials	Check if 'alice' and 'secret' match	Match found	Credentials valid	None
4	Generate token	User 'alice'	None	Token created	access_token='abc123'
5	Return token response	access_token='abc123'	None	Response sent	{'access_token': 'abc123', 'token_type': 'bearer'}
6	User uses token	Authorization: Bearer abc123	Token valid	Access granted	API data
7	If credentials invalid	username='bob', password='wrong'	No match	Credentials invalid	Error 401 Unauthorized

💡 Execution stops after token is returned or error sent based on credential check.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	Final
username	None	'alice'	'alice'	'alice'	'alice'
password	None	'secret'	'secret'	'secret'	'secret'
credentials_valid	False	False	True	True	True
access_token	None	None	None	'abc123'	'abc123'

Key Moments - 3 Insights

Why does the server return an error instead of a token sometimes?

If the credentials do not match any user (see execution_table step 7), the server returns an error instead of generating a token.

What happens if the password is correct but username is wrong?

The server checks both username and password together (step 3). If either is wrong, credentials are invalid and no token is generated.

When is the access token created?

The token is created only after credentials are verified as valid (step 4). Before that, no token exists.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'credentials_valid' after step 3?

A False

B None

C True

D Error

💡 Hint

Check the 'Result' column at step 3 in the execution_table.

At which step does the server send the access token back to the user?

A Step 5

B Step 4

C Step 2

D Step 6

💡 Hint

Look for the step where 'Response sent' is in the 'Result' column.

If the password is wrong, which step shows the server's response?

A Step 5

B Step 7

C Step 3

D Step 6

💡 Hint

Check the row where 'Credentials invalid' and 'Error 401 Unauthorized' appear.

Concept Snapshot

OAuth2 password flow in FastAPI:
- User sends username & password to /token via POST
- Server verifies credentials
- If valid, server returns access token
- User uses token to access protected API
- If invalid, server returns error
Use OAuth2PasswordRequestForm for input parsing.

Full Transcript

In OAuth2 password flow using FastAPI, the user sends their username and password to the /token endpoint via a POST request. The server extracts these credentials and checks if they match a known user. If the credentials are valid, the server generates an access token and sends it back in the response. The user then uses this token to access protected API routes. If the credentials are invalid, the server returns an error response instead of a token. This flow ensures only authorized users get access tokens to use the API.

Practice

1. What is the main purpose of the OAuth2 password flow in FastAPI?

easy

A. To allow users to log in by sending their username and password directly to the app.

B. To register new users automatically without credentials.

C. To refresh access tokens without user interaction.

D. To encrypt user passwords before storing them.

Solution

1. Step 1: Understand OAuth2 password flow purpose

   This flow lets users send their username and password to the app to get an access token.

2. Step 2: Compare options with flow purpose

   Only To allow users to log in by sending their username and password directly to the app. describes this direct login method; others describe different features.

3. Final Answer:

   To allow users to log in by sending their username and password directly to the app. -> Option A

4. Quick Check:

   OAuth2 password flow = direct login [OK]

Hint: Password flow means user sends username and password [OK]

Common Mistakes:

• Confusing password flow with token refresh
• Thinking it registers users automatically
• Assuming it encrypts passwords by itself

2. Which FastAPI import is used to handle OAuth2 password flow form data?

easy

A. from fastapi.security import OAuth2PasswordBearer

B. from fastapi.security import OAuth2PasswordRequestForm

C. from fastapi.security import HTTPBasicCredentials

D. from fastapi.security import APIKeyHeader

Solution

1. Step 1: Identify form class for password flow

   FastAPI uses OAuth2PasswordRequestForm to parse username and password from form data.

2. Step 2: Check other imports

   OAuth2PasswordBearer is for token extraction, HTTPBasicCredentials is for basic auth, APIKeyHeader is for API keys.

3. Final Answer:

   from fastapi.security import OAuth2PasswordRequestForm -> Option B

4. Quick Check:

   Form data handler = OAuth2PasswordRequestForm [OK]

Hint: Password flow form uses OAuth2PasswordRequestForm [OK]

Common Mistakes:

• Using OAuth2PasswordBearer instead of RequestForm
• Confusing HTTPBasicCredentials with OAuth2 forms
• Importing unrelated security classes

3. Given this FastAPI endpoint using OAuth2 password flow, what will be the response if username is 'alice' and password is 'secret'?

from fastapi import FastAPI, Depends
from fastapi.security import OAuth2PasswordRequestForm

app = FastAPI()

@app.post('/token')
async def login(form_data: OAuth2PasswordRequestForm = Depends()):
    if form_data.username == 'alice' and form_data.password == 'secret':
        return {'access_token': 'token123', 'token_type': 'bearer'}
    return {'error': 'Invalid credentials'}

medium

A. {'access_token': 'token123', 'token_type': 'bearer'}

B. {'error': 'Invalid credentials'}

C. HTTP 422 Unprocessable Entity error

D. Empty response with status 204

Solution

1. Step 1: Check input credentials against condition

   The code checks if username is 'alice' and password is 'secret'. Given inputs match this.

2. Step 2: Determine returned response

   Since condition is true, it returns the access token dictionary with 'token123' and 'bearer'.

3. Final Answer:

   {'access_token': 'token123', 'token_type': 'bearer'} -> Option A

4. Quick Check:

   Correct credentials = access token response [OK]

Hint: Match username and password to get token response [OK]

Common Mistakes:

• Assuming error response for correct credentials
• Confusing HTTP errors with normal returns
• Ignoring the if condition logic

4. What is wrong with this FastAPI OAuth2 password flow code snippet?

from fastapi import FastAPI, Depends
from fastapi.security import OAuth2PasswordRequestForm

app = FastAPI()

@app.post('/token')
async def login(form_data: OAuth2PasswordRequestForm):
    if form_data.username == 'bob' and form_data.password == 'pass':
        return {'access_token': 'abc', 'token_type': 'bearer'}
    return {'error': 'Invalid'}

medium

A. Endpoint should use GET method instead of POST

B. Incorrect import of OAuth2PasswordRequestForm

C. Return type should be a string, not dict

D. Missing Depends() in function parameter for form_data

Solution

1. Step 1: Check function parameter for dependency injection

   OAuth2PasswordRequestForm must be wrapped with Depends() to extract form data properly.

2. Step 2: Verify other parts

   Imports are correct, return type as dict is valid JSON response, POST method is correct for token requests.

3. Final Answer:

   Missing Depends() in function parameter for form_data -> Option D

4. Quick Check:

   Use Depends() to get form data [OK]

Hint: Always wrap OAuth2PasswordRequestForm with Depends() [OK]

Common Mistakes:

• Forgetting Depends() causes runtime errors
• Using GET instead of POST for token endpoint
• Thinking return must be string, not dict

5. You want to secure a FastAPI endpoint so only users with a valid OAuth2 password flow token can access it. Which approach correctly uses OAuth2PasswordBearer and token verification?

from fastapi import FastAPI, Depends, HTTPException
from fastapi.security import OAuth2PasswordBearer

app = FastAPI()
oauth2_scheme = OAuth2PasswordBearer(tokenUrl='token')

def verify_token(token: str):
    if token != 'validtoken':
        raise HTTPException(status_code=401, detail='Invalid token')

@app.get('/secure-data')
async def secure_data(token: str = Depends(oauth2_scheme)):
    verify_token(token)
    return {'data': 'secret info'}

hard

A. Incorrect: verify_token should return True/False, not raise exceptions.

B. Incorrect: tokenUrl should be '/secure-data' not 'token'.

C. Correct: uses OAuth2PasswordBearer and verifies token before returning data.

D. Incorrect: OAuth2PasswordBearer cannot be used with GET endpoints.

Solution

1. Step 1: Check OAuth2PasswordBearer usage

   oauth2_scheme is created with tokenUrl='token', which is correct for password flow token endpoint.

2. Step 2: Verify token validation logic

   verify_token raises HTTPException on invalid token, which is proper for access control.

3. Step 3: Confirm endpoint dependency and response

   secure_data depends on oauth2_scheme to get token, verifies it, then returns protected data.

4. Final Answer:

   Correct: uses OAuth2PasswordBearer and verifies token before returning data. -> Option C

5. Quick Check:

   Use OAuth2PasswordBearer + verify token = secure endpoint [OK]

Hint: Use OAuth2PasswordBearer with tokenUrl and verify token [OK]

Common Mistakes:

• Setting wrong tokenUrl in OAuth2PasswordBearer
• Not raising exceptions on invalid token
• Thinking OAuth2PasswordBearer can't be used with GET