Header precedence

When the same header is set in more than one place, Bright uses the value from the source with the highest priority. Sources with a lower priority do not overwrite it. From highest to lowest:

1. Authorized requests setup in the authentication object.
2. Additional Headers in the Discovery settings (Target specific settings).
3. Global Auth Flow Headers in the Advanced Settings of the authentication object.
4. Protected Resource Request Headers on the Authentication Validation tab of the authentication object.
5. Headers whose value comes from a baseline parameter.
6. Headers from an imported HAR file.