From 951f50afa4318b0e7de573c5ca806fa2e1192759 Mon Sep 17 00:00:00 2001 From: Brian Erickson Date: Thu, 25 Apr 2024 08:16:39 -0600 Subject: [PATCH 1/3] Updated Auth readme to fix broken link --- Authentication/External_Token_Auth/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Authentication/External_Token_Auth/README.md b/Authentication/External_Token_Auth/README.md index 1ac2733..4ee1b21 100644 --- a/Authentication/External_Token_Auth/README.md +++ b/Authentication/External_Token_Auth/README.md @@ -6,7 +6,7 @@ To support this type of authentication, HawkScan supports externally supplying a The external supplied authorization token can be used in conjunction with either `cookieAuthorization` or `tokenAuthorization`. This scenario will use `tokenAuthorization`, a custom header for the authorization token and pass an externally generated token from our web application’s JWT library. This will allow us to run HawkScan as any user of our application in a programatic fashion. -For more help configuring External Token Authentication, see our [Documentation](https://docs.stackhawk.com/hawkscan/configuration/authenticated-scanning.html#external-token-authentication--custom-token-authorization) +For more help configuring External Token Authentication, see our [Documentation](https://docs.stackhawk.com/hawkscan/authenticated-scanning/inject-cookies-and-tokens.html) #### Running the scanner with multiiple config files To better support advanced configurations you can provide multiple configuration files as an overlay to the base scan configuration `stackhawk.yml`. Subsequent configuration files will be merged on top of the prior, effectively replacing any duplicate setting values form the previous scan configuration file. From e82707944f0bba43cd4bd9d511fdda47fd5e687e Mon Sep 17 00:00:00 2001 From: Brian Erickson Date: Thu, 25 Apr 2024 08:18:32 -0600 Subject: [PATCH 2/3] fixed some spelling issues --- Authentication/External_Token_Auth/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Authentication/External_Token_Auth/README.md b/Authentication/External_Token_Auth/README.md index 4ee1b21..11415fb 100644 --- a/Authentication/External_Token_Auth/README.md +++ b/Authentication/External_Token_Auth/README.md @@ -4,11 +4,11 @@ Sometimes authentication is not performed with just a `username` and `password`. To support this type of authentication, HawkScan supports externally supplying an authorization token with the authentication.external configuration. -The external supplied authorization token can be used in conjunction with either `cookieAuthorization` or `tokenAuthorization`. This scenario will use `tokenAuthorization`, a custom header for the authorization token and pass an externally generated token from our web application’s JWT library. This will allow us to run HawkScan as any user of our application in a programatic fashion. +The external supplied authorization token can be used in conjunction with either `cookieAuthorization` or `tokenAuthorization`. This scenario will use `tokenAuthorization`, a custom header for the authorization token and pass an externally generated token from our web application’s JWT library. This will allow us to run HawkScan as any user of our application in a programmatic fashion. For more help configuring External Token Authentication, see our [Documentation](https://docs.stackhawk.com/hawkscan/authenticated-scanning/inject-cookies-and-tokens.html) -#### Running the scanner with multiiple config files +#### Running the scanner with multiple config files To better support advanced configurations you can provide multiple configuration files as an overlay to the base scan configuration `stackhawk.yml`. Subsequent configuration files will be merged on top of the prior, effectively replacing any duplicate setting values form the previous scan configuration file. ``` From d21ab3109e479c93712bc7d476e347e047fcbe69 Mon Sep 17 00:00:00 2001 From: Brian Erickson Date: Thu, 25 Apr 2024 08:32:30 -0600 Subject: [PATCH 3/3] Adjust link to correct (non-deprecated) URL Co-authored-by: d-co-white <98342720+d-co-white@users.noreply.github.com> --- Authentication/External_Token_Auth/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Authentication/External_Token_Auth/README.md b/Authentication/External_Token_Auth/README.md index 11415fb..b138e88 100644 --- a/Authentication/External_Token_Auth/README.md +++ b/Authentication/External_Token_Auth/README.md @@ -6,7 +6,7 @@ To support this type of authentication, HawkScan supports externally supplying a The external supplied authorization token can be used in conjunction with either `cookieAuthorization` or `tokenAuthorization`. This scenario will use `tokenAuthorization`, a custom header for the authorization token and pass an externally generated token from our web application’s JWT library. This will allow us to run HawkScan as any user of our application in a programmatic fashion. -For more help configuring External Token Authentication, see our [Documentation](https://docs.stackhawk.com/hawkscan/authenticated-scanning/inject-cookies-and-tokens.html) +For more help configuring External Token Authentication, see our [Documentation](https://docs.stackhawk.com/hawkscan/authenticated-scanning/inject-multiple-cookies-and-tokens.html) #### Running the scanner with multiple config files To better support advanced configurations you can provide multiple configuration files as an overlay to the base scan configuration `stackhawk.yml`. Subsequent configuration files will be merged on top of the prior, effectively replacing any duplicate setting values form the previous scan configuration file.