Newman does not include header pre-set at collection level

[kavippriya2021 (Kavippriya R)]

Your question may already have an answer on the community forum. Please search for related topics, and then read through the guidelines before creating a new topic.

Here’s an outline with best practices for making your inquiry.

My question:
the tests that require bearer token in authorization header does not work as expected when run from newman. I have a collection where i am send client credentials in OAuth 2.0 and the generated token as the bearer token in the authorization header. When run from postman it works fine but failing to authorize when run from newman.

Details (like screenshots):

How I found the problem:
While automating one of the client application

I’ve already tried:
Unable to find a work around for this issue

[michaelderekjones (Mike Jones)]

Where is that token being stored?

If its an environment variable. Are you including the environment json in the Newman command line parameters?

[mrcarracedo (Charo Carracedo)]

Hello. I am facing the same issue or very similar one.
JWT auth calculates the token ok for Postman, but fails in Newman. Here is the evidence in Postman

And the evidence that in Newman execution, the Authorization header is not included