You can use the header authentication method if the login-protected resources within the application you want to scan require one or more static header authentication tokens, which are generated outside of Bright.
In case a specified authentication token expires, the authentication object will no longer provide Bright with the ability to reach authenticated resources of that particular target.
This topic describes only how to fill in fields specific for header form authentication (the Setup tab). For general steps, see Creating Authentication.
From the Authentication type dropdown list, select Header authentication, and then add the authentication Headers.
|Merge Strategy||Select whether the specified header must be replaced or appended before sending each request, for example, authentication cookies.|
|Name||Select an additional header to be replaced or appended before sending each request, |
|Value||Enter the header value.|
- You can add as many headers as you need by clicking + Add header at the bottom of the Headers section.
- To delete a header, click next to the corresponding header field.
There are cases when MFA is required ONLY on initial IP login. This means that our scan IP can be validated once and will not require any further MFA validations. For that case, you need to identify which cookie supports the completed MFA/2FA and include a valid cookie as a part of your authentication object.
Bright allows testing a scan before saving it. For details, see the Testing Authentication.
Updated about 2 months ago