OAuth 2.0 flow in Postman - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

OAuth 2.0: Purpose of Authorization Code

In the OAuth 2.0 Authorization Code flow, what is the main purpose of the authorization code?

A It is a refresh token used to get new access tokens after expiration.

B It is the final token used to access protected resources directly.

C It is a temporary code used to obtain an access token securely without exposing user credentials.

D It is a client secret used to authenticate the client application.

💡 Hint

Think about why the authorization code is exchanged for an access token instead of using it directly.

The authorization code is a temporary code that the client receives after user authorization. It is exchanged securely for an access token, which is then used to access protected resources. This prevents exposing user credentials or tokens in the browser.

❓ Predict Output

intermediate

Postman: OAuth 2.0 Access Token Retrieval Result

Given this Postman OAuth 2.0 token request setup, what will be the result if the client_id or client_secret is incorrect?

Postman

POST /oauth/token HTTP/1.1
Host: auth.example.com
Content-Type: application/x-www-form-urlencoded

client_id=wrong_id&client_secret=wrong_secret&grant_type=authorization_code&code=abc123&redirect_uri=https://app.example.com/callback

A {"error":"invalid_client","error_description":"Client authentication failed"}

B {"access_token":"xyz789","token_type":"Bearer","expires_in":3600}

C HTTP 500 Internal Server Error

D {"error":"invalid_grant","error_description":"Authorization code expired"}

💡 Hint

Consider what happens when client credentials are wrong during token exchange.

If the client_id or client_secret is incorrect, the authorization server responds with an 'invalid_client' error indicating client authentication failure.

❓ assertion

advanced

Validating OAuth 2.0 Access Token Response in Postman Test Script

Which Postman test script assertion correctly verifies that the access token is present and is a non-empty string in the OAuth 2.0 token response?

Postman

pm.test("Access token is present and valid", function () {
    const jsonData = pm.response.json();
    // Assertion goes here
});

A pm.expect(jsonData.access_token).to.exist.and.equal(true);

B pm.expect(jsonData.access_token).to.be.a('string').and.not.empty;

C pm.expect(jsonData.access_token).to.be.undefined;

D pm.expect(jsonData.access_token.length).to.be.above(10);

💡 Hint

Check for type string and that it is not empty.

Option B correctly asserts that the access_token exists, is a string, and is not empty. Option B incorrectly checks if it equals true. Option B expects it to be undefined which is wrong. Option B checks length but does not verify type or presence.

🔧 Debug

advanced

Debugging OAuth 2.0 Token Expiry Handling in Postman

You have a Postman test script that checks if the access token expires in less than 5 minutes and fails the test if so. The script is:

pm.test("Token expiry is sufficient", function () {
    const jsonData = pm.response.json();
    pm.expect(jsonData.expires_in & 300).to.be.true;
});

What is the issue with this script?

A The test incorrectly expects expires_in to be less than 300 seconds.

B The test should check for jsonData.access_token instead of expires_in.

C The pm.expect syntax is invalid and will cause a syntax error.

D The bitwise AND operator (&) is used instead of the greater than operator (>), causing incorrect evaluation.

💡 Hint

Look carefully at the operator used in the assertion.

The script uses the bitwise AND operator (&) instead of the greater than operator (>). This causes the expression to evaluate incorrectly, leading to wrong test results.

❓ framework

expert

Automating OAuth 2.0 Authorization Code Flow in Postman Collection Runner

Which approach correctly automates the OAuth 2.0 Authorization Code flow in Postman Collection Runner to obtain and use access tokens dynamically?

A Use a pre-request script to request the authorization code manually, then exchange it for an access token and save it to an environment variable for subsequent requests.

B Manually copy the access token from the browser and paste it into Postman environment variables before running the collection.

C Set the access token as a global variable once and reuse it indefinitely without refreshing.

D Use Postman's built-in OAuth 2.0 token helper to get the token once and hardcode it in the Authorization header.

💡 Hint

Think about how to automate token retrieval and usage dynamically in Postman scripts.

Option A describes the correct automation approach: using pre-request scripts to programmatically obtain the authorization code and exchange it for an access token, then saving it for use in requests. Other options rely on manual or static token usage, which is not automation.