Home
AppScan Presence
An AppScan Presence on your server enables you to scan sites not accessible from the Internet, and to incorporate scanning as part of your functional testing.
Legacy AppScan Presence
This section describes the legacy version of the AppScan Presence, V1. This version will be supported only until October 1, 2022.
Activating the Proxy Server
To use the Proxy Server in the AppScan Presence, you must activate it, and configure the port.

AppScan Presence
An AppScan Presence on your server enables you to scan sites not accessible from the Internet, and to incorporate scanning as part of your functional testing.
- System requirements
- Creating the Presence
  For private web apps, or for including a scan as part of your functional testing procedure, you must create an AppScan Presence, with access to the web app or back-end server, and to the Internet. Proxy connections are supported.
- Starting the Presence
- Configuring Private Site Server proxy
  If your private network requires the Private Site Server to use a proxy to connect with the web app or back-end server (internal proxy), or with the Internet (outgoing proxy), configure it as follows.
- Configuring a PAC file
  If a proxy auto-config (PAC) file is required in order to reach the various domains in your site, configure the AppScan Presence as follows.
- Renewing the Presence key
  When you originally download the presence, it includes a key to activate it. When that key expires, you must replace it with a valid key.
- Log files
- Upgrading to the new AppScan Presence
  If you already have a V1 AppScan Presence installed and you want to upgrade to V2, follow these instructions.
- Legacy AppScan Presence
  This section describes the legacy version of the AppScan Presence, V1. This version will be supported only until October 1, 2022.
  - System requirements for the legacy Presence
  - Creating the legacy Presence
    For private web apps, or for including a scan as part of your functional testing procedure, you must create an AppScan Presence, with access to the web app or back-end server, and to the Internet. Proxy connections are supported.
  - Starting the legacy Presence
  - Activating the Proxy Server
    To use the Proxy Server in the AppScan Presence, you must activate it, and configure the port.
  - Using the Proxy Server
    You can use the AppScan Presence Proxy Server to record traffic, save it as a DAST.CONFIG file, and import it to run an ASoC scan. You can optionally encrypt this file, as described in a sub-section below.
  - Configuring Private Site Server proxy (legacy Presence)
    If your private network requires the Private Site Server to use a proxy to connect with the web app or back-end server (internal proxy), or with the Internet (outgoing proxy), configure it as follows.
  - Configuring a PAC file (legacy Presence)
    If a proxy auto-config (PAC) file is required in order to reach the various domains in your site, configure the AppScan Presence as follows.
  - Renewing the Presence key (legacy Presence)
    When you originally download the presence, it includes a key to activate it. When that key expires, you must replace it with a valid key.

Activating the Proxy Server

To use the Proxy Server in the AppScan Presence, you must activate it, and configure the port.

About this task

Note: When making changes to the configuration properties file, make sure to remove the "#" signs at the beginning of any line you edit.

Procedure

Download the latest version of Node.js and install it on your machine.
In the root folder of the AppScan Presence, locate config.properties and open it with a text editor.
To activate the Proxy Server, locate this line:
```
##proxyServerEnabled = false
```
and change it to this:
```
proxyServerEnabled = true
```
To change the Proxy Server port, change this line:
```
##proxyServerPort = 8383
```
to this:
```
proxyServerPort = [new port number]
```
Note: To have a random available port selected each time, set proxyServerPort = 0
If the site is available on the Internet, disable the Private Site Server by changing this:
```
##privateSiteServerEnabled = true
```
to this:
```
privateSiteServerEnabled = false
```
If the presence was running while you made the configuration changes, you must terminate (Ctrl + C) for the changes to take effect.
Start the Presence.