Configuring a Private Site Server Proxy for the HCL AppScan Traffic Recorder

If your private network requires the Private Site Server to use a proxy to connect with the web application or back-end server (internal proxy), or with the Internet (outgoing proxy), configure it as follows.

About this task

Figure 1. Scanning a secure network that requires a proxy connection
Proxy configuration

For details of how private site scanning works "under the hood," refer to Understanding Private Site Scanning

Procedure

  1. In the root folder of the presence, locate appsettings.json and open it with a text editor.
  2. Add the settings by removing the // at the start of each relevant line, and save the file.
    "Host" can be a name or an IP address.

    For example, to configure internal proxy IP 192.168.1.100, and port 3128, edit:

    //"InternalProxyEndpoint": {
        //  "Host": "localhost",
        //  "Port": 8899
        //},
    
    to
    "InternalProxyEndpoint": {
          "Host": "192.168.1.100",
          "Port": 3128
        },
    
    Note: Configuring both an internal proxy and a PAC file is not supported.
  3. If the HCL AppScan Traffic Recorder is running, terminate it (Ctrl + C) for the changes to take effect, and then restart it.