OAuth 2.0 flow in Postman - Test Execution Trace

Test Overview

This test checks the OAuth 2.0 authorization code flow in Postman. It verifies that the access token is successfully retrieved and can be used to access a protected API endpoint.

Test Code - Postman

Postman

pm.test("OAuth 2.0 Access Token Retrieval and API Access", function () {
    // Step 1: Request access token using authorization code
    pm.sendRequest({
        url: pm.environment.get('token_url'),
        method: 'POST',
        header: {
            'Content-Type': 'application/x-www-form-urlencoded'
        },
        body: {
            mode: 'urlencoded',
            urlencoded: [
                { key: 'grant_type', value: 'authorization_code' },
                { key: 'code', value: pm.environment.get('auth_code') },
                { key: 'redirect_uri', value: pm.environment.get('redirect_uri') },
                { key: 'client_id', value: pm.environment.get('client_id') },
                { key: 'client_secret', value: pm.environment.get('client_secret') }
            ]
        }
    }, function (err, res) {
        pm.expect(err).to.be.null;
        pm.expect(res).to.have.property('status', 200);
        const jsonData = res.json();
        pm.expect(jsonData).to.have.property('access_token');
        pm.environment.set('access_token', jsonData.access_token);

        // Step 2: Use access token to call protected API
        pm.sendRequest({
            url: pm.environment.get('protected_api_url'),
            method: 'GET',
            header: {
                'Authorization': `Bearer ${jsonData.access_token}`
            }
        }, function (err2, res2) {
            pm.expect(err2).to.be.null;
            pm.expect(res2).to.have.property('status', 200);
            pm.test('Protected API returns expected data', function () {
                const apiData = res2.json();
                pm.expect(apiData).to.have.property('user');
            });
        });
    });
});

Execution Trace - 4 Steps

Step	Action	System State	Assertion	Result
1	Send POST request to token endpoint with authorization code and client credentials	Postman sends request to token_url with correct headers and body	Response status code is 200 and contains access_token	PASS
2	Extract access_token from response and save to environment variable	access_token stored in Postman environment	access_token is not empty or null	PASS
3	Send GET request to protected API endpoint with Bearer token authorization header	Postman sends request to protected_api_url with Authorization header	Response status code is 200	PASS
4	Verify protected API response contains expected user data	Response JSON includes 'user' property	'user' property exists in response JSON	PASS

Failure Scenario

Failing Condition: Authorization code is invalid or expired, or client credentials are incorrect

Execution Trace Quiz - 3 Questions

What is the first step in the OAuth 2.0 flow tested here?

A Refreshing the access token

B Calling the protected API without a token

C Requesting an access token using the authorization code

D Logging out the user

Key Result

Always verify that the access token is correctly retrieved before using it to access protected resources. This ensures the OAuth 2.0 flow is working end-to-end.

Practice

1. What is the primary purpose of the OAuth 2.0 flow in Postman?

easy

A. To create user accounts automatically

B. To encrypt API requests for better security

C. To generate random API keys for testing

D. To securely authorize access to APIs without sharing user credentials

Solution

1. Step 1: Understand OAuth 2.0 role

   OAuth 2.0 is designed to allow applications to access resources on behalf of a user without exposing their password.

2. Step 2: Identify Postman's use of OAuth 2.0

   Postman uses OAuth 2.0 flow to get access tokens that authorize API calls securely.

3. Final Answer:

   To securely authorize access to APIs without sharing user credentials -> Option D

4. Quick Check:

   OAuth 2.0 = Secure API authorization [OK]

Hint: OAuth 2.0 is about authorization, not encryption or keys [OK]

Common Mistakes:

• Confusing OAuth with encryption
• Thinking OAuth generates API keys
• Assuming OAuth creates user accounts

2. Which of the following is the correct way to set the OAuth 2.0 token URL in Postman?

easy

A. http//api.example.com/oauth/token

B. api.example.com/oauth/token

C. https://api.example.com/oauth/token

D. https://api.example.com/oauth/token/

Solution

1. Step 1: Check URL format

   The token URL must be a full valid URL starting with https:// for security.

2. Step 2: Validate options

   https://api.example.com/oauth/token is a full valid URL with https and no trailing slash, which is standard.

3. Final Answer:

   https://api.example.com/oauth/token -> Option C

4. Quick Check:

   Full HTTPS URL = Correct token URL [OK]

Hint: Always use full HTTPS URL for token endpoint [OK]

Common Mistakes:

• Omitting https:// prefix
• Using incorrect URL syntax
• Adding unnecessary trailing slash

3. In Postman, after configuring OAuth 2.0 with client ID, client secret, and token URL, what will happen when you click Get New Access Token?

medium

A. Postman sends a request to the token URL and retrieves an access token if credentials are valid

B. Postman creates a new user account automatically

C. Postman encrypts the client secret and saves it locally without sending a request

D. Postman resets all environment variables

Solution

1. Step 1: Understand the Get New Access Token button

   This button triggers Postman to request an access token from the OAuth server using provided credentials.

2. Step 2: Identify expected behavior

   If credentials are valid, the server returns an access token which Postman stores for API calls.

3. Final Answer:

   Postman sends a request to the token URL and retrieves an access token if credentials are valid -> Option A

4. Quick Check:

   Get New Access Token = Request token from server [OK]

Hint: Get New Access Token requests token from server [OK]

Common Mistakes:

• Thinking it creates user accounts
• Assuming it only encrypts data locally
• Confusing it with environment reset

4. You configured OAuth 2.0 in Postman but get an error: invalid_client. What is the most likely cause?

medium

A. Token URL is missing https:// prefix

B. Incorrect client ID or client secret provided

C. Access token expired

D. Postman environment variables are empty

Solution

1. Step 1: Analyze the error message

   The error invalid_client means the OAuth server rejected the client credentials.

2. Step 2: Identify common causes

   Most often this happens when client ID or secret is wrong or mistyped.

3. Final Answer:

   Incorrect client ID or client secret provided -> Option B

4. Quick Check:

   invalid_client = Wrong client credentials [OK]

Hint: Check client ID and secret first on invalid_client error [OK]

Common Mistakes:

• Assuming token expiration causes invalid_client
• Ignoring https:// in token URL
• Blaming environment variables without checking credentials

5. You want to automate API testing in Postman using OAuth 2.0. Which approach correctly handles token expiration during tests?

hard

A. Use a pre-request script to check token expiry and request a new token automatically

B. Manually get a new token before each test run

C. Hardcode the access token in headers and never refresh it

D. Disable OAuth and use basic authentication instead

Solution

1. Step 1: Understand token expiration problem

   Access tokens expire, so tests must handle refreshing tokens automatically to avoid failures.

2. Step 2: Identify automation solution in Postman

   Using a pre-request script to check token expiry and request a new token ensures tests always have valid tokens.

3. Final Answer:

   Use a pre-request script to check token expiry and request a new token automatically -> Option A

4. Quick Check:

   Automate token refresh with pre-request script [OK]

Hint: Automate token refresh with pre-request scripts [OK]

Common Mistakes:

• Manually refreshing tokens slows automation
• Hardcoding tokens causes failures on expiry
• Switching auth methods ignores OAuth benefits