Inheriting auth from collection in Postman - Build an Automation Script

Verify that a request inherits authentication from its collection

Preconditions (2)

Step 1: Open the Postman app and select the collection with authentication configured

Step 2: Select a request inside the collection that does not have its own authentication settings

Step 3: Send the request

Step 4: Observe the request headers or authorization tab to confirm the authentication is applied

Step 5: Verify the response status code is 200 OK or as expected for authenticated requests

✅ Expected Result: The request uses the authentication settings inherited from the collection and successfully authenticates, returning the expected response.

Automation Requirements - Postman test scripts (JavaScript)

Assertions Needed:

Verify the Authorization header is present in the request

Verify the response status code is 200

Verify the response body contains expected authenticated content

Best Practices:

Use pm.request.headers to check headers

Use pm.response.to.have.status to assert status code

Use pm.expect for assertions

Keep test scripts simple and clear

Automated Solution

Postman

pm.test('Authorization header is present', () => {
    const authHeader = pm.request.headers.get('Authorization');
    pm.expect(authHeader).to.not.be.undefined;
    pm.expect(authHeader).to.not.be.empty;
});

pm.test('Response status is 200', () => {
    pm.response.to.have.status(200);
});

pm.test('Response body contains authenticated content', () => {
    const jsonData = pm.response.json();
    pm.expect(jsonData).to.have.property('user');
    pm.expect(jsonData.user).to.have.property('id');
});

This test script runs after the request is sent.

First, it checks if the Authorization header is present in the request headers, confirming the request inherited the auth from the collection.

Second, it asserts the response status code is 200, meaning the request was successful and authenticated.

Third, it verifies the response body contains a user object with an id property, which is expected only if authentication succeeded.

These checks together confirm that the request correctly inherited authentication from the collection.

Common Mistakes - 3 Pitfalls

{'mistake': 'Checking for authentication in the request body instead of headers', 'why_bad': 'Authentication tokens are sent in headers, not in the request body, so this check will fail or be meaningless.', 'correct_approach': "Check the 'Authorization' header in pm.request.headers to verify authentication."}

Hardcoding expected response status without verifying actual API behavior

Not checking if the request actually inherited auth and assuming it did

Bonus Challenge

Now add data-driven testing with 3 different requests in the collection, each inheriting auth and verifying their own expected response content.

Show Hint

Practice

1. What does it mean to inherit authentication from a collection in Postman?

easy

A. Requests use the collection's saved login details automatically.

B. Each request must have its own separate authentication setup.

C. Authentication is disabled for all requests in the collection.

D. Authentication details are shared only between environments.

Solution

1. Step 1: Understand collection-level authentication

   Collection-level authentication means login info is saved once for all requests inside it.

2. Step 2: Apply inheritance concept to requests

   Requests automatically use this saved info unless overridden individually.

3. Final Answer:

   Requests use the collection's saved login details automatically. -> Option A

4. Quick Check:

   Inheriting auth = Requests use collection auth [OK]

Hint: Remember: collection auth applies to all requests by default [OK]

Common Mistakes:

• Thinking each request needs separate auth setup
• Assuming auth is disabled when inherited
• Confusing environment variables with collection auth

2. Which of the following is the correct way to set a request to inherit authentication from its collection in Postman?

easy

A. Leave the request's auth type blank.

B. Set the request's auth type to 'Inherit auth from parent'.

C. Manually enter the collection's auth details in the request.

D. Disable authentication on the request.

Solution

1. Step 1: Identify the correct auth setting for inheritance

   Postman provides an explicit option called 'Inherit auth from parent' to use collection auth.

2. Step 2: Understand why other options are incorrect

   Leaving blank or disabling auth does not inherit; manual entry duplicates info.

3. Final Answer:

   Set the request's auth type to 'Inherit auth from parent'. -> Option B

4. Quick Check:

   Auth inheritance = 'Inherit auth from parent' [OK]

Hint: Choose 'Inherit auth from parent' to reuse collection auth [OK]

Common Mistakes:

• Leaving auth blank expecting inheritance
• Copying auth details manually into each request
• Disabling auth thinking it inherits

3. Given a collection with Basic Auth username 'user1' and password 'pass1', what will be the Authorization header value for a request set to inherit auth from this collection?

medium

A. Authorization: Digest user1:pass1

B. Authorization: Bearer dXNlcjE6cGFzczE=

C. Authorization: Basic user1:pass1

D. Authorization: Basic dXNlcjE6cGFzczE=

Solution

1. Step 1: Understand Basic Auth header format

   Basic Auth uses 'Authorization: Basic ' plus base64 encoding of 'username:password'.

2. Step 2: Encode 'user1:pass1' in base64

   Encoding 'user1:pass1' results in 'dXNlcjE6cGFzczE='.

3. Final Answer:

   Authorization: Basic dXNlcjE6cGFzczE= -> Option D

4. Quick Check:

   Basic Auth header = 'Basic ' + base64(username:password) [OK]

Hint: Basic Auth header = 'Basic ' + base64(username:password) [OK]

Common Mistakes:

• Confusing Basic with Bearer or Digest schemes
• Using plain 'user:pass' without encoding
• Encoding incorrectly or forgetting colon

4. You set a request to inherit auth from its collection, but the request fails with 401 Unauthorized. What is the most likely cause?

medium

A. The request URL is invalid.

B. The request has its own auth set, overriding the collection.

C. The collection's authentication details are incorrect or expired.

D. Postman does not support auth inheritance.

Solution

1. Step 1: Check collection auth correctness

   If collection auth is wrong or expired, inherited requests will fail authentication.

2. Step 2: Rule out other causes

   Request auth overriding would not inherit; URL invalid causes different error; Postman supports inheritance.

3. Final Answer:

   The collection's authentication details are incorrect or expired. -> Option C

4. Quick Check:

   401 error + inherited auth = bad collection credentials [OK]

Hint: Check collection auth details first on 401 errors [OK]

Common Mistakes:

• Assuming inheritance is not supported
• Ignoring collection auth validity
• Blaming request URL without checking auth

5. You have a collection with OAuth 2.0 authentication set. You want one request to use a different token without changing the collection. How should you configure this request?

hard

A. Set the request's auth type to OAuth 2.0 and enter the new token manually.

B. Keep the request set to inherit auth from collection and change the collection token.

C. Disable authentication on the request.

D. Create a new collection with the new token.

Solution

1. Step 1: Understand overriding auth at request level

   To use a different token, the request must have its own auth settings, not inherit.

2. Step 2: Apply OAuth 2.0 with new token on request

   Set request auth type to OAuth 2.0 and input the new token manually to override collection.

3. Final Answer:

   Set the request's auth type to OAuth 2.0 and enter the new token manually. -> Option A

4. Quick Check:

   Override collection auth by setting request auth explicitly [OK]

Hint: Override collection auth by setting request auth manually [OK]

Common Mistakes:

• Changing collection token affects all requests
• Disabling auth causes request to fail
• Creating new collection unnecessarily