Bearer token authentication in Rest API - Step-by-Step Execution

Concept Flow - Bearer token authentication

Client sends request

↓

Check Authorization header

↓

Extract Bearer token

↓

Validate token

↓

Allow access

↓

Send response

The client sends a request with a Bearer token in the Authorization header. The server extracts and validates the token, then allows or denies access accordingly.

Execution Sample

Rest API

GET /api/data HTTP/1.1
Authorization: Bearer abc123token

// Server extracts 'abc123token'
// Server validates token
// Server responds with data if valid

This example shows a client sending a GET request with a Bearer token, which the server checks before responding.

Execution Table

Step	Action	Input/Condition	Result/Output
1	Receive HTTP request	Authorization header present	Header read: 'Bearer abc123token'
2	Extract token	Header value 'Bearer abc123token'	Token extracted: 'abc123token'
3	Validate token	Token 'abc123token'	Token is valid
4	Authorize request	Token valid	Access granted
5	Send response	Access granted	200 OK with requested data
6	End	Request processed	Execution stops

💡 Request processing ends after sending response based on token validation

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
Authorization header	None	'Bearer abc123token'	'Bearer abc123token'	'Bearer abc123token'
Token	None	'abc123token'	'abc123token'	'abc123token'
Token valid?	Unknown	Unknown	True	True
Access granted?	False	False	True	True

Key Moments - 2 Insights

Why do we extract the token from the Authorization header?

Because the token is sent as part of the Authorization header with the prefix 'Bearer '. We must remove 'Bearer ' to get the actual token string, as shown in step 2 of the execution_table.

What happens if the token is invalid?

If the token is invalid, the server denies access and sends an error response instead of the requested data. This is the alternative path after step 3 in the concept_flow.

Visual Quiz - 3 Questions

Look at the execution_table, what is the token value after step 2?

A 'abc123token'

B None

C 'Bearer abc123token'

D 'token abc123'

💡 Hint

Check the 'Token' variable value in variable_tracker after step 2

At which step does the server decide to grant access?

A Step 1

B Step 3

C Step 4

D Step 5

💡 Hint

Look at the 'Authorize request' action in execution_table

If the Authorization header was missing, what would happen?

A Token would be empty but access granted

B Token extraction would fail and access would be denied

C Server would ignore authentication and allow access

D Server would crash

💡 Hint

Refer to concept_flow where Authorization header is checked first

Concept Snapshot

Bearer token authentication uses the Authorization header with 'Bearer <token>'.
The server extracts the token, validates it, and grants or denies access.
If token is valid, server responds with requested data.
If invalid or missing, server denies access with error.
This method secures API endpoints simply and effectively.

Full Transcript

Bearer token authentication works by the client sending a token in the Authorization header of an HTTP request. The header looks like 'Authorization: Bearer abc123token'. The server reads this header, extracts the token by removing the 'Bearer ' prefix, and then checks if the token is valid. If the token is valid, the server allows access to the requested resource and sends back the data with a 200 OK response. If the token is invalid or missing, the server denies access and sends an error response. This process ensures only authorized clients can access protected API endpoints.

Practice

1. What is the main purpose of a Bearer token in REST API authentication?

easy

A. To prove the identity of the client making the request

B. To encrypt the data sent between client and server

C. To specify the format of the response data

D. To define the API endpoint URL

Solution

1. Step 1: Understand Bearer token role

   A Bearer token is a secret key sent with requests to prove who the client is.

2. Step 2: Identify main purpose

   It helps the server know the client's identity and permissions.

3. Final Answer:

   To prove the identity of the client making the request -> Option A

4. Quick Check:

   Bearer token = client identity proof [OK]

Hint: Bearer tokens prove who you are, not encrypt data [OK]

Common Mistakes:

• Thinking Bearer tokens encrypt data
• Confusing token with API endpoint
• Assuming token defines response format

2. Which of the following is the correct way to include a Bearer token in an HTTP request header?

easy

A. Token: Bearer your_token_here

B. Authorization: Bearer your_token_here

C. Authorization: Token your_token_here

D. Bearer: Authorization your_token_here

Solution

1. Step 1: Recall Bearer token header format

   The standard way is to use the 'Authorization' header with the word 'Bearer' followed by the token.

2. Step 2: Match correct syntax

   Authorization: Bearer your_token_here matches the correct syntax: 'Authorization: Bearer your_token_here'.

3. Final Answer:

   Authorization: Bearer your_token_here -> Option B

4. Quick Check:

   Authorization header + Bearer keyword = correct format [OK]

Hint: Use 'Authorization: Bearer <token>' exactly [OK]

Common Mistakes:

• Using 'Token' instead of 'Bearer'
• Swapping header name and value order
• Omitting 'Bearer' keyword

3. Given this Python code snippet using the requests library, what will be the output if the token is invalid?

import requests
headers = {"Authorization": "Bearer invalid_token"}
response = requests.get("https://api.example.com/data", headers=headers)
print(response.status_code)

medium

A. 200

B. 404

C. 401

D. 500

Solution

1. Step 1: Understand HTTP status codes for authentication

   401 means Unauthorized, which is returned when authentication fails due to invalid token.

2. Step 2: Analyze the code behavior with invalid token

   The server will reject the request and respond with 401 Unauthorized status code.

3. Final Answer:

   401 -> Option C

4. Quick Check:

   Invalid token = 401 Unauthorized [OK]

Hint: Invalid token usually returns 401 status code [OK]

Common Mistakes:

• Assuming 200 means success with invalid token
• Confusing 404 Not Found with authentication error
• Thinking server error 500 occurs for invalid token

4. You wrote this code to send a Bearer token but the server always responds with 401 Unauthorized. What is the likely error?

headers = {"Authorization": "bearer mytoken123"}
response = requests.get(url, headers=headers)

medium

A. The URL is incorrect

B. The token string is missing

C. The header name should be 'Token' instead of 'Authorization'

D. The word 'bearer' should be capitalized as 'Bearer'

Solution

1. Step 1: Check Bearer token header case sensitivity

   The 'Bearer' keyword in the Authorization header is case sensitive and must be capitalized.

2. Step 2: Identify the error in the code

   The code uses 'bearer' in lowercase, causing the server to reject the token and respond 401.

3. Final Answer:

   The word 'bearer' should be capitalized as 'Bearer' -> Option D

4. Quick Check:

   Bearer keyword is case sensitive [OK]

Hint: Capitalize 'Bearer' exactly in Authorization header [OK]

Common Mistakes:

• Using lowercase 'bearer' keyword
• Changing header name from 'Authorization'
• Ignoring token format errors

5. You want to secure an API endpoint so only requests with a valid Bearer token can access it. Which of these is the best approach to implement this in your REST API server?

hard

A. Check the 'Authorization' header for a Bearer token, validate it, and reject requests without valid tokens

B. Allow all requests but log the Bearer token if present

C. Require the token as a URL query parameter instead of header

D. Ignore tokens and rely on IP address filtering

Solution

1. Step 1: Understand secure API access with Bearer tokens

   Secure APIs check the Authorization header for a valid Bearer token to authenticate requests.

2. Step 2: Identify best practice for token validation

   Rejecting requests without valid tokens ensures only authorized clients access the endpoint.

3. Final Answer:

   Check the 'Authorization' header for a Bearer token, validate it, and reject requests without valid tokens -> Option A

4. Quick Check:

   Validate token in Authorization header to secure API [OK]

Hint: Validate Bearer token in Authorization header to secure API [OK]

Common Mistakes:

• Using query parameters for tokens (less secure)
• Allowing requests without token validation
• Relying on IP filtering alone