Post-Installation

Before proceeding further, the Secure Gateway needs to be manually configured to point to your Plant SCADA Access Anywhere Server. To do this:

1. Edit the config.js file located on the computer where the Secure Gateway is installed. This file is located in the following folder.

   \Program Files (x86)\AVEVA Plant SCADA Access Anywhere\Plant SCADA Access Anywhere Secure Gateway\WebServer\PlantAccessAnywhere\

2. Find the commented line:

   // address:"", // Address of server

3. Uncomment the line by removing the initial "//".

4. Within the quotation marks, type the name or IP address of the computer on which the Plant SCADA Access Anywhere Server is installed.
   For example:

   address: "VD-CA-SRV", // Address of server

Access to the Plant SCADA Access Anywhere Server is routed through the Secure Gateway node. When you navigate to the https://<Name or IP Address of the computer where the Secure Gateway is installed>/, the following page appears:

This login dialog will function differently depending on the value of the ‘Authentication Server’ settings, discussed in more detail later.

In brief, if the Secure Gateway is configured to use an Authentication Server, it will authenticate users before passing the credentials on to the Plant SCADA Access Anywhere Server.

If the Secure Gateway is not configured to use an Authentication Server, the credentials will be passed directly to the Plant SCADA Access Anywhere Server for authentication.

Although subtle, these settings may make a big difference if the Secure Gateway and Plant SCADA Access Anywhere Servers are located in different domains, or have other differences in their authentication capabilities.

When logging in, you will need to prefix your username with your domain name, or, if there is a common domain name, you can enter it in the config.js file, under the ‘Domain’ entry, for example:

DOMAIN: "domain.com", // Optional domain for RDP Session…

The Administration page for the Authentication Server, showing the current status, and the domain name that it is authorizing against, can be viewed at https://localhost:7443/Admin with a local administrator login.

Note: A page refresh and clearing cookies on every client are required each time the Address property in the config.js is changed.