Configure Properties to Use Reverse Proxy

Cisco Secure Application automatically interprets the APM agent setting for an HTTP Proxy server and uses the same server for communication between the agent and Controller. However, you must configure these settings for the APM agent to communicate with Controller through a reverse proxy:

Note: The reverse proxy configuration may change based on the reverse proxy solution that you use. Ensure that you use a pass-through reverse proxy to forward any requests containing /argento-agent/v1 or auth/v1/oauth to <tenant-name>.saas.appdynamics.com. These steps are not applicable for the .NET Agent because the .NET Agent does not support reverse proxy.

In the JVM, configure the reverse proxy details for Cisco Secure Application:
1. Specify the reverse proxy URL:
```
-Dargento.management.server.reverse.proxy.url=http://<reverse-proxy-host>:<reverse-proxy-port>/
```
  Here, reverse-proxy-host and reverse-proxy-port are the hostname and port of the reverse proxy that will direct communications to the Controller.
2. Specify the domain:
```
-Dargento.management.server.add.headers=Host:<tenant-name>.saas.appdynamics.com
```
  Here, tenant-name is the tenant name of the Controller.
In the JVM, configure these Cisco Secure Application system properties to use the reverse proxy:
- Dargento.management.server.authentication.access.key
```
-Dargento.management.server.authentication.access.key=<access-key>
```
  Here, access-key is the access key specific to the tenant.
- Dargento.management.server.authentication.user
```
-Dargento.management.server.authentication.user=singularity-agent@<tenant-name>
```
  Here, tenant-name is the tenant name of the Controller.