ITAA_Gateway_AdminManual
ITAA_Gateway_AdminManual
InTouch® Access
Anywhere Secure
Gateway
Administrator Manual
10/13/14
All rights reserved. No part of this documentation shall be reproduced, stored in a retrieval system, or
transmitted by any means, electronic, mechanical, photocopying, recording, or otherwise, without the
prior written permission of Invensys Systems, Inc. No copyright or patent liability is assumed with respect
to the use of the information contained herein. Although every precaution has been taken in the
preparation of this documentation, the publisher and the author assume no responsibility for errors or
omissions. Neither is any liability assumed for damages resulting from the use of the information
contained herein.
The information in this documentation is subject to change without notice and does not represent a
commitment on the part of Invensys Systems, Inc. The software described in this documentation is
furnished under a license or nondisclosure agreement. This software may be used or copied only in
accordance with the terms of these agreements.
Contents
Welcome .................................................... 5
Documentation Conventions ........................................................... 6
Technical Support ............................................................................ 6
Chapter 2 Installation.................................................. 9
Prerequisites .................................................................................... 9
Secure Gateway Installation ......................................................... 10
Secure Gateway Configuration ...................................................... 11
Uninstalling the Secure Gateway ................................................. 12
Welcome
• Wonderware® InTouch®
• Enabling and configuring RDP on Windows operating systems
• Firewall configuration
• Web server administration
Important terminology includes the following:
• DMZ (demilitarized zone) - a physical or logical subnetwork that
contains and exposes an organization’s external services to a larger
untrusted network.
• HTML5 - a new update to the HTML specification. Extends HTML
with new features and functionality for communication, display
and more.
• RDP - Remote Desktop Protocol. A remote display protocol
developed by Microsoft. RDP is a standard component of Microsoft
Windows.
• RDP Host - a Windows system that can be remotely accessed using
Microsoft RDP, such as a Terminal Server (RDP Session Host) or
Windows workstation with remote access enabled.
• SSL - Secure Sockets Layer is a cryptographic protocol that
provides communications security over the Internet.
Documentation Conventions
This documentation uses the following conventions:
Technical Support
Wonderware Technical Support offers a variety of support options to
answer any questions on Wonderware products and their
implementation.
Before you contact Technical Support, refer to the relevant section(s)
in this documentation for a possible solution to the problem. If you
need to contact technical support for help, have the following
information ready:
• The type and version of the operating system you are using.
• Details of how to recreate the problem.
• The exact wording of the error messages you saw.
• Any relevant output listing from the Log Viewer or any other
diagnostic applications.
• Details of what you did to try to solve the problem(s) and your
results.
• If known, the Wonderware Technical Support case number
assigned to your problem, if this is an ongoing problem.
Chapter 1
Introduction
Architecture
Secure Gateway acts as a gateway between users in remote locations
and applications in the control network. Secure Gateway can be
installed in a DMZ to route traffic between a business network and an
HMI SCADA network.
The following diagram illustrates how the Secure Gateway uses a
single port for secured remote access. All communication related web
traffic and session protocols are tunneled through the SSL based
Secure Gateway connection.
Chapter 2
Installation
This chapter describes the process for installing the Secure Gateway.
It includes prerequisites needed for installation, a step-by-step
procedure, details for configuration, and instructions for uninstalling
the Secure Gateway.
Prerequisites
The Secure Gateway requires Windows Server 2003 or higher.
.NET Framework 4 Full Installation is also required and can be
downloaded from Microsoft's website, at:
http://www.microsoft.com/en-us/download/details.aspx?id=17851
Secure Gateway uses port 443 by default. This is a common port that
is also used by IIS, so check for port conflicts.
The following ports need to be configured on the network.
• Port 443 is required between the external network and the Secure
Gateway server; this value is adjustable.
• For InTouch Access Anywhere Server: Port 8080 is required
between the Secure Gateway Server and the InTouch Access
Anywhere Server; this value is adjustable.
The Secure Gateway includes an HTTP proxy that listens on port 80
by default. This can be disabled post-installation.
4 Click Next.
Installation will proceed.
5 Click Finish.
Chapter 3
3 In the Program path and filename field, enter "view.exe" and the
path for the InTouch application you want to open. For example:
view.exe "c:\MyInTouchApps\newapp2"
Note: The start page can be renamed to any valid file name but for
better readability,we recommend prefixing the file name, with the
InTouch Access Anywhere server name. For example, if the server
name is Master01, the start page should be renamed to
Master01_start.html.
Chapter 4
Configuration Portal
Dashboard
Secure Gateway Configuration Dashboard displays useful statistics
related to the Secure Gateway operation. Open this page to view
server uptime, SSL certificate status, session activity, and to restart
the Secure Gateway Server service.
Mail Alerts
Secure Gateway can be configured to send e-mail alerts upon specified
system events. To configure mail alerts, enter the SMTP information
of the e-mail server. Then check the desired parameters that will
trigger the sending of a mail alert.
Click Save or Save and Test Mail Settings to apply the configuration.
Configuration
Follow these steps to enable the use of a Secure Gateway with InTouch
Access Anywhere:
At the client browser, click the Advanced button in the Connection
Details page.
Select Use InTouch Access Anywhere Secure Gateway and
provide the Gateway address:
Advanced Configuration
All configurable settings related to the Secure Gateway may be found
in the EricomSecureGateway.exe.config file. This is a text file that can
be opened with a text editor. The configuration settings are also
defined in the seciton "Built-InAuthentication Server" on page 24
Changing parameter values marked as "Reloadable" do not require a
service restart. "Not Reloadable" parameters will only take effect after
the next service restarts.
High Availability
To provide high availability to the Secure Gateway layer, it is
recommended that you install two or more Secure Gateways and use a
third-party redundant load balancer to manage access.
The load balancer will provide one address for end users. As requests
arrive at the load balancer, they will be redirected to an available
Secure Gateway based on built-in weighting criteria. A basic
round-robin load balancer may also be used, but it may not detect
whether a Secure Gateway is active.
If the target is a relative URL, it will replace the "/sso" portion in the
path.
If the target is a full URL, it will completely replace the current path.
Built-InAuthentication Server
The Secure Gateway includes an Authentication Server which
provides a layer of security by authenticating end-users before they
contact any internal resource (for example, the InTouch Access
Anywhere Server).
The Authentication Server is installed on a server that is a member of
the domain and which is employed to authenticate users.
Setting Description
Chapter 5
6 Save the file and the new Thumbprint will be used. Restarting the
Secure Gateway service will apply the new certificate immediately.
The Thumbprint can also be manually typed in.
Note: The DNS address of the Secure Gateway server must match the
certificate name. If it does not, a “Connection failed” error message will
appear upon attempting a connection.
Note: Maintain uptime for the servers at the front of the list to ensure
the fastest login time. If the primary server is unavailable, end-users
will experience longer login time, as the login process must wait for the
primary server to timeout before attempting to connect to a failover
server.
Chapter 6
The Secure Gateway has a built-in Web server which supports the
ability to host the web pages for certain products such as InTouch
Access Anywhere. The built-in Web server cannot be disabled and
always listens on the Secure Gateway port.
To configure the Web server, open the Configuration tool and go to
Web Server.
Click the drop down box to select the default URL for the built-in Web
Server. Click Save. When the user goes to the root path of the URL,
the selected component will be used.
Note: Using the Secure Gateway to proxy to pages other than InTouch
Access Anywhere is not officially supported.
HTTP Redirect
The InTouch Access Anywhere Secure Gateway Web server listens on
port 80 by default. This way, HTTP references to the server will
automatically redirect to the HTTPS URL.
To enable this feature, check the setting: Enabled non-secured port for
HTTPS auto-redirect (see below).
Advanced Configuration
Back up the current EricomSecureGateway.exe.config file before
making any changes.
To configure the settings of the built-in Web server, open the
EricomSecureGateway.exe.config using a text editor. Each folder in
the WebServer directory may have a default document assigned for it,
and may also be restricted so that end users cannot access it.
<internalWebServerSettings>
<Folders default_folder="View"
allow_access_for_non_listed_folders="false">
<add folder_name="AccessAnywhere" default_page="start.html"
allow_access="true"/>
<add folder_name="View" default_page="view.html"
allow_access="true"/>
<add folder_name="Blaze" default_page="blaze.exe"
allow_access="false"/>
<add folder_name="MyCustom" default_page="hello.html"
allow_access="false"/>
</Folders> </internalWebServerSettings>
Chapter 7
Known Limitations
If this error appears, check the address that is being used for the
InTouch Access Anywhere Secure Gateway. If it is an IP address, like
the image shown below, it may pose a problem.
Rather than using the IP address, use a domain name that matches a
trusted certificate that has been configured in the InTouch Access
Anywhere Secure Gateway.
Note: The logs require a special viewer which can be downloaded from
the Download page
The current log file is accessible using the Configuration page under
the Download tab. The actual log detail levels may be set under the
two log pages (Log Settings - Basic and Log Settings- Advanced).
Consult with a support engineer on which settings to enable.