Reverse Proxy (Gateway) installation
Prerequisites
The installation of the ShareAspace Reverse Proxy (Gateway) requires the following prerequisites:
- Hardware prerequisites for a Web Server (IIS).
- Software prerequisites for a Web Server (IIS).
- TLS Certificate for the Web Server (IIS).
- Trust for the TLS certificate used by the ShareAspace Host.
- HTTPS in IIS.

Note
To install the Gateway, a ShareAspace Host endpoint is required. Ensure that a ShareAspace Host is installed and accessible.
Installation steps
Step 1: Run the installer
Run the ReverseProxy.msi installer to install the ShareAspace Reverse Proxy on the IIS server.
Step 2: Configure IIS
During installation, an IIS Application Pool named "ReverseProxy" is created.
By default, the Application Pool runs under the built-in ApplicationPoolIdentity account.
Note
If a different account is used for the "ReverseProxy" Application Pool, it must have read access to the installation folder.
Step 3: Verify installation
Verify that the Reverse Proxy is accessible and correctly routes requests to the ShareAspace Host.
Example:
GET https://gateway.machine.net/api
Configuration
- Open the
appsettings.jsonfile located in the ShareAspace Reverse Proxy installation folder.- By default:
C:\Program Files\Eurostep\ShareAspace\ReverseProxy\appsettings.json.
- By default:
- Set the ShareAspace Host node address under:
ReverseProxy/Clusters/Destinations/ShareAspaceCluster/destination1/Address- For example:
https://host.machine.net:5001.
- When running in failover mode, the Reverse Proxy must be configured with the primary and all secondary ShareAspace Host nodes. Additional health check configuration is also required.
Example
{
...
"ReverseProxy": {
...
"Clusters": {
"ShareAspaceCluster": {
...
"Destinations": {
"ShareAspaceCluster/destination1": {
"Address": "https://host.machine.net:5001"
}
}
}
}
}
}
Failover configuration
When running in failover mode, the Reverse Proxy must be configured with the primary node and all secondary nodes. Additional configuration for the health check process is also required.
{
...
"ReverseProxy": {
...
"Clusters": {
"ShareAspaceCluster": {
"LoadBalancingPolicy": "First",
"HttpClient": {
"DangerousAcceptAnyServerCertificate": true
},
"HealthCheck": {
"Active": {
"Enabled": "true",
"Interval": "00:00:10",
"Timeout": "00:00:10",
"Policy": "PrimarySecondary",
"Path": "/health"
}
},
"Metadata": {
"ConsecutiveFailuresHealthPolicy.Threshold": "3"
},
"Destinations": {
"ShareAspaceCluster/destination1": {
"Address": "_HOSTURI_"
},
"ShareAspaceCluster/destination2": {
"Address": "_HOSTURI_"
}
}
}
}
}
}
| Placeholder | Description | Example value |
|---|---|---|
_HOSTURI_ |
ShareAspace host node address. destination1 is treated as the primary node. |
https://esaz123N1:5001 |
HealthCheck/Active/Enabled– Enables health checks when set to"true"ConsecutiveFailuresHealthPolicy.Threshold– Number of failed checks before failover is triggered