OAuth2 password flow in FastAPI - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is OAuth2 password flow in FastAPI?

OAuth2 password flow is a way for users to log in by sending their username and password directly to the server, which then returns an access token to use for future requests.

beginner

Which FastAPI class helps implement OAuth2 password flow?

The class OAuth2PasswordBearer is used to define the token URL and handle token extraction from requests in OAuth2 password flow.

beginner

Why should passwords never be stored in plain text in OAuth2 password flow?

Storing passwords in plain text is unsafe because if the database is leaked, attackers get all passwords. Instead, passwords should be hashed to protect user data.

intermediate

What is the role of the token URL in OAuth2 password flow?

The token URL is the endpoint where the client sends username and password to get an access token. FastAPI uses this URL to handle login requests.

intermediate

How does FastAPI verify the access token after OAuth2 password flow?

FastAPI uses dependency injection with OAuth2PasswordBearer to extract the token from requests and verify it before allowing access to protected routes.

In OAuth2 password flow, what does the client send to the token URL?

A Username and password

B Only username

C Only password

D Access token

The client sends both username and password to the token URL to get an access token.

Which FastAPI class is used to extract the token from requests in OAuth2 password flow?

A OAuth2PasswordRequestForm

B OAuth2ClientCredentials

C OAuth2AuthorizationCodeBearer

D OAuth2PasswordBearer

OAuth2PasswordBearer extracts the token from the request headers.

Why is hashing passwords important in OAuth2 password flow?

A To protect passwords if the database leaks

B To store passwords in plain text

C To speed up login

D To make passwords visible to admins

Hashing protects passwords so attackers cannot read them if the database is compromised.

What does FastAPI return after successful OAuth2 password flow login?

A User's password

B Access token

C Refresh token only

D User profile data

FastAPI returns an access token to authorize future requests.

Which HTTP method is typically used to send credentials to the token URL in OAuth2 password flow?

A GET

B PUT

C POST

D DELETE

POST method is used to securely send username and password to the token URL.

Explain how OAuth2 password flow works in FastAPI from login to token verification.

Think about the steps from user login to accessing protected routes.

Describe why it is important to hash passwords and how FastAPI handles token extraction in OAuth2 password flow.

Focus on security and token handling.

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