The eperi sEcure Platform requires connection to the Internet, in order to access your SaaS
application. If you are using an upstream proxy within your corporate network, it is
necessary to configure your upstream proxy within the eperi sEcure Platform.
Before you begin
You used the automated installation packages to install the
Gateway.
Procedure
-
Connect to the target server using your preferred ssh tool (e.g. putty) and log
in.
-
Modify the file
/opt/eperi/gateway/tomcat/conf/javaopts.
-
Add the following to the first line of the file and replace
<port> and <hostname> with the
actual values for your upstream proxy:
-Dhttp.proxyPort=<port> -Dhttp.proxyHost=<hostname> -Dhttp.proxySet=true
-Dhttps.proxyPort=<port> -Dhttps.proxyHost=<hostname> -Dhttps.proxySet=true
-
(Optional) If required, add the following property to the line above and
replace <mydomain.com> with your internal DNS domain in order to bypass
the upstream proxy for internal hosts:
-Dhttp.nonProxyHosts="localhost|127.*|[::1]|*.<mydomain.com>"
Note: If this property is not explicitly defined, all common variations of the
loopback address are already excluded by default.
-
(Optional) If your upstream proxy server requires authentication, Basic
Authentication credentials can be passed on by adding the following properties
to the line above:
-Dhttp.proxyUser=<myuser> -Dhttp.proxyPassword=<mypassword>
-Dhttps.proxyUser=<myuser> -Dhttps.proxyPassword=<mypassword>
-
Restart the eperi sEcure Platform by executing the following command:
sudo systemctl restart eperi-gateway
Important: In a cluster setup, the changes must be made on every
eperi sEcure Platform instance and each eperi sEcure Platform instance must be
restarted.
Results
You have configured the eperi sEcure Platform, so that it
can access the Internet (and your SaaS application) via your upstream proxy.