How do I configure my Authentication Verifier agent to use a proxy?

This document is for:

Invicti Enterprise On-Demand, Invicti Enterprise On-Premises

If your Authentication Verifier agent is in a network with an outbound proxy or WAF, its outbound traffic may get blocked without correct configuration.

You may also see log messages such as the following example:

2024-01-30 18:41:12.0714 | Error | acunetix-687bcf56cf-lm54s | 14 | 34 | 24.1.0 | 8efb914c-a49b-4cba-92ca-b1070402272a | Invicti.Cloud.Agent.Scanning.TaskManager| Unable to launch scan task 8efb914c-a49b-4cba-92ca-b1070402272a

System.ArgumentNullException: Value cannot be null. (Parameter 'path')

Keep in mind that the preferred way to handle your scenario is to implement the appropriate whitelisting to allow outbound traffic for your agent.

Confirm that outbound traffic is being blocked

If your Authentication Verifier agent is installed on a machine that can run a browser, you can launch the agent's internal browser to confirm that outbound traffic is being blocked:

Using a test website in these examples, this is what the test website would like with a regular chrome browser:

…whereas using the Authentication Verifier agent's built-in chrome you might get the following if the outbound traffic is just dropped:

…or you might get something like this if your WAF informs you of the block:

Adjusting your Agent settings

To configure your agent to pass through your configured proxy or WAF:

open your appsettings.json file and locate the ProxySettings section, and:

adjust the ProxyMode value to CustomProxy
set the values of the Username, Password, Domain, Address, and Port to your outbound proxy or WAF values