Bug Report
Current behavior:
In the authorization request, the script saves the token in a variable called OAuth2, while the environment and the test cases always reference the variable as oauth.
Expected behavior:
The variable name used by the script should match the one defined in the environment and test cases, i.e. oauth.
Steps to reproduce:
- Run the authorization request
- Check the variable where the token is saved — it will be stored as
OAuth2
- Run any test case or check the environment — the expected variable is
oauth
- The token won't be picked up correctly due to the name mismatch
Related code:
// Current script
postman.setEnvironmentVariable("OAuth2", "Bearer " + json.data.access_token);
Other information:
Variable name mismatch between the auth script and the rest of the collection. Likely causing auth failures in any TC that depends on this token. Check all requests that reference oauth or OAuth2 to ensure consistency.
Bug Report
Current behavior:
In the authorization request, the script saves the token in a variable called
OAuth2, while the environment and the test cases always reference the variable asoauth.Expected behavior:
The variable name used by the script should match the one defined in the environment and test cases, i.e.
oauth.Steps to reproduce:
OAuth2oauthRelated code:
Other information:
Variable name mismatch between the auth script and the rest of the collection. Likely causing auth failures in any TC that depends on this token. Check all requests that reference
oauthorOAuth2to ensure consistency.