Token refresh mechanism in Rest API - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to extract the refresh token from the request headers.

Rest API

refresh_token = request.headers.get([1])

Drag options to blanks, or click blank then click option'

A"Content-Type"

B"Authorization"

C"Refresh-Token"

D"User-Agent"

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'Authorization' header instead of 'Refresh-Token'.

Trying to get the token from 'Content-Type' header.

The refresh token is usually sent in a custom header like Refresh-Token. Using request.headers.get("Refresh-Token") retrieves it.

2fill in blank

medium

Complete the code to verify if the refresh token is valid before issuing a new access token.

Rest API

if not verify_token([1]):
    return {'error': 'Invalid refresh token'}, 401

Drag options to blanks, or click blank then click option'

Arefresh_token

Baccess_token

Cuser_id

Drequest_token

Attempts:

3 left

💡 Hint

Common Mistakes

Verifying the access token instead of the refresh token.

Using an undefined variable like 'request_token'.

We verify the refresh_token to ensure it is valid before issuing a new access token.

3fill in blank

hard

Fix the error in the code that generates a new access token using the user ID from the refresh token payload.

Rest API

user_id = decode_token([1])['user_id']
new_access_token = generate_access_token(user_id)

Drag options to blanks, or click blank then click option'

Apayload

Brefresh_token

Crequest.headers

Daccess_token

Attempts:

3 left

💡 Hint

Common Mistakes

Decoding the access token instead of the refresh token.

Trying to decode the entire request headers.

The refresh_token must be decoded to extract the user_id for generating a new access token.

4fill in blank

hard

Fill both blanks to create a JSON response with the new access token.

Rest API

return { [1]: [2] }

Drag options to blanks, or click blank then click option'

A"access_token"

B"message": "Token refreshed successfully"}

Cnew_access_token

D"access_token": new_access_token

Attempts:

3 left

💡 Hint

Common Mistakes

Returning a string instead of a dictionary.

Using incorrect keys or missing braces.

The response should be a JSON object with the key access_token and the new token as its value.

5fill in blank

hard

Fill all three blanks to implement a complete token refresh endpoint that extracts, verifies, decodes, and returns a new access token.

Rest API

def refresh_token_endpoint(request):
    [1] = request.headers.get("Refresh-Token")
    if not verify_token([2]):
        return {'error': 'Invalid refresh token'}, 401
    user_id = decode_token([3])['user_id']
    new_access_token = generate_access_token(user_id)
    return {'access_token': new_access_token}

Drag options to blanks, or click blank then click option'

Arefresh_token

Daccess_token

Attempts:

3 left

💡 Hint

Common Mistakes

Using different variable names for the refresh token in different places.

Confusing access token with refresh token.

All blanks should be filled with refresh_token to correctly handle the token refresh process.

Practice

1. What is the main purpose of a refresh token in a token refresh mechanism?

easy

A. To obtain a new access token without asking the user to log in again

B. To log out the user immediately

C. To store user passwords securely

D. To encrypt the access token

Solution

1. Step 1: Understand the role of refresh tokens

   Refresh tokens are used to get new access tokens when the old ones expire without requiring the user to log in again.

2. Step 2: Compare options with this role

   Only To obtain a new access token without asking the user to log in again describes this purpose correctly. Options A, C, and D describe unrelated or incorrect functions.

3. Final Answer:

   To obtain a new access token without asking the user to log in again -> Option A

4. Quick Check:

   Refresh token = renew access token without login [OK]

Hint: Refresh tokens renew access tokens silently [OK]

Common Mistakes:

• Confusing refresh token with access token
• Thinking refresh token logs out users
• Believing refresh token stores passwords

2. Which HTTP method is typically used by clients to send a refresh token to the server for a new access token?

easy

A. GET

B. PUT

C. POST

D. DELETE

Solution

1. Step 1: Identify the HTTP method for sending data securely

   POST is used to send data like refresh tokens in the request body securely to the server.

2. Step 2: Eliminate other methods

   GET is for retrieving data, DELETE for removing resources, and PUT for updating. Refresh token requests usually send sensitive data, so POST is preferred.

3. Final Answer:

   POST -> Option C

4. Quick Check:

   Send refresh token securely = POST [OK]

Hint: Use POST to send refresh tokens securely [OK]

Common Mistakes:

• Using GET which exposes tokens in URL
• Confusing PUT with POST
• Using DELETE which is for removal

3. Consider this simplified server response code snippet handling a refresh token request:

if refresh_token == valid_token:
    access_token = generate_new_token()
    return {"access_token": access_token, "status": 200}
else:
    return {"error": "Invalid refresh token", "status": 401}

What will be the output if refresh_token is invalid?

medium

A. {"access_token": "newtoken123", "status": 200}

B. {"error": "Invalid refresh token", "status": 401}

C. SyntaxError

D. {"status": 200}

Solution

1. Step 1: Analyze the condition for refresh token validity

   If the refresh token matches the valid token, a new access token is generated and returned with status 200.

2. Step 2: Check the else branch for invalid token

   If the token is invalid, the code returns an error message with status 401.

3. Final Answer:

   {"error": "Invalid refresh token", "status": 401} -> Option B

4. Quick Check:

   Invalid token returns error 401 [OK]

Hint: Invalid token triggers error response 401 [OK]

Common Mistakes:

• Assuming new token is returned even if invalid
• Confusing status codes 200 and 401
• Expecting syntax errors from valid code

4. A developer wrote this code to refresh tokens but it always returns an error:

def refresh_access_token(refresh_token):
    if refresh_token = valid_token:
        return generate_new_token()
    else:
        return "Invalid token"

What is the main error in this code?

medium

A. Function should not take parameters

B. Missing return statement in else block

C. generate_new_token() is undefined

D. Using assignment (=) instead of comparison (==) in the if condition

Solution

1. Step 1: Check the if condition syntax

   The code uses a single equals sign (=) which is assignment, not comparison. This causes a syntax error or logic error.

2. Step 2: Confirm other parts are correct

   The else block has a return statement, generate_new_token() is assumed defined, and function parameters are correct.

3. Final Answer:

   Using assignment (=) instead of comparison (==) in the if condition -> Option D

4. Quick Check:

   Use '==' to compare, not '=' [OK]

Hint: Use '==' for comparison in conditions [OK]

Common Mistakes:

• Confusing '=' with '==' in if statements
• Assuming missing return in else
• Thinking function parameters are wrong

5. You want to implement a token refresh endpoint that rejects refresh tokens if they are expired or revoked. Which approach best ensures security and proper token refresh?

hard

A. Store refresh tokens with expiration and revocation status; verify both before issuing new access tokens

B. Accept any refresh token and always issue a new access token

C. Only check if the refresh token exists in the database, ignore expiration

D. Issue new access tokens without any refresh token verification

Solution

1. Step 1: Understand security needs for refresh tokens

   Refresh tokens must be checked for expiration and revocation to prevent misuse and unauthorized access.

2. Step 2: Evaluate options for token verification

   Store refresh tokens with expiration and revocation status; verify both before issuing new access tokens includes both expiration and revocation checks, ensuring only valid tokens get new access tokens. Other options ignore important security checks.

3. Final Answer:

   Store refresh tokens with expiration and revocation status; verify both before issuing new access tokens -> Option A

4. Quick Check:

   Verify expiration and revocation for security [OK]

Hint: Check expiration and revocation before refresh [OK]

Common Mistakes:

• Ignoring token expiration
• Not checking if token is revoked
• Issuing tokens without verification