Home › Technical articles

Đọc bằng tiếng Việt

InTouch Access Anywhere and the Secure Gateway: browser access, ports, certificates, limits, 2026 status

TDL Industrial Automation · Last updated:

From AVEVA's System Platform 2023 R2 SP2 documentation, the newest set that still describes it: the Access Anywhere Server on the RDS host, the Secure Gateway in the DMZ, the Authentication Server, ports 443, 8080 and 80, InTouch TSE licensing, certificates, allowlists, display settings, limitations and troubleshooting; discontinued as of System Platform 2026.

InTouch Access Anywhere shows InTouch applications and AVEVA OMI ViewApps in an HTML5 web browser, with no client software on the device. The Access Anywhere Server runs on a Remote Desktop Services (RDS) host and turns each RDP session into WebSocket traffic, and an optional Secure Gateway in the DMZ gives remote users one encrypted port. AVEVA discontinued the product with System Platform 2026, so this article follows the newest AVEVA documentation that still describes it, the System Platform 2023 R2 SP2 set, for plants that still run it.

InTouch Access Anywhere through the Secure GatewayThree network zones from top to bottom. Outside zone (business network or internet): an HTML5 browser on a PC, tablet or phone, with no client software, connects with HTTPS and secure WebSocket to the Secure Gateway on TCP port 443. DMZ: the Secure Gateway, with one SSL certificate for every host behind it, the Configuration Portal at /admin, an HTTP proxy on port 80 that redirects to HTTPS, and high availability through a load balancer or a failover list. From the gateway, an optional user-authentication link goes to the Authentication Server, which sits on the safe side of the firewall, is off by default and admits domain users only. The gateway connects by WebSocket, SSL optional, on TCP port 8080 to the RDS host in the control network. The RDS host runs the InTouch Access Anywhere Server, which translates RDP into WebSocket; each browser session is a WindowViewer session of an InTouch application or an AVEVA OMI ViewApp and uses one RDP session and one InTouch TSE licence. A browser on the plant network or over a VPN connects directly to the server by WebSocket on TCP port 8080. Below the RDS host are the Galaxy, I/O servers and PLCs the applications already use. Based on AVEVA System Platform 2023 R2 SP2 documentation; the product is discontinued as of System Platform 2026.InTouch Access Anywhere through the Secure GatewayBusiness network or internetRemote browserHTML5 on a PC, tablet or phone; noclient softwareDMZ (perimeter network)Secure Gatewayone SSL certificate for all hosts behind itConfiguration Portal at /adminHTTP proxy on port 80 redirects to HTTPShigh availability: load balancer or failover listHTTPS, secure WebSocket · TCP 443Control network, safe side of the firewallRDS hostInTouch Access Anywhere Server: RDPtranslated to WebSocketWindowViewersessionInTouchapplication, 10.6or laterOMI ViewAppsessionViewApp fromSystem Platform2017 or latereach browser session: one RDP session andone InTouch TSE licenceWebSocket, SSL optional · TCP 8080Galaxy, I/O servers and PLCsthe data the InTouch applications andViewApps already useAuthentication Serveroptional, off by default; domainmember, domain users onlyuser authentication (optional)Browser in the plantplant network, or over a VPN thatsupports WebSocketsport 8080Based on AVEVA, OMI, InTouch HMI and System Platform 2023 R2 SP2 documentation (read 17November 2026). Ports shown are defaults; 443 and 8080 can be changed. InTouch Access Anywhere isdiscontinued as of System Platform 2026. Figure: drawn by TDL.
Figure 1: InTouch Access Anywhere through the Secure Gateway. On a phone, swipe sideways to see the whole figure.

1. What it is, and its status in 2026

In the 2023 R2 SP2 documentation, Access Anywhere gives remote access from desktops, laptops, tablets and phones. AVEVA lists image compression, packet shaping and whole-frame rendering for network performance, touch gestures and a session toolbar. It can show OMI ViewApps made with System Platform 2017 or later, and InTouch applications built with version 10.6 or later.

AVEVA's browser lists differ between pages. The InTouch requirements name Safari, Chrome, Edge, Internet Explorer, Firefox and Opera as validated; the OMI pages give two different sets of tested versions, and AVEVA advises a recent version.

The OMI 2026 release notes state that InTouch Access Anywhere is discontinued as of System Platform 2026. The InTouch HMI 2026 notes say it is not available for security reasons and is not on the System Platform 2026 installation media. The 2026 list of System Platform ports no longer has Access Anywhere entries. For browser access, the 2026 documentation describes the AVEVA web client, covered in AVEVA OMI or InTouch HMI.

2. The three components

Component Where AVEVA places it What it does
Access Anywhere Server on the RDS host that runs InTouch WindowViewer or the ViewApps translates RDP into WebSocket; browsers connect to it directly or through the Secure Gateway
Secure Gateway (optional) on a separate computer in the DMZ one secure port for remote users, one SSL certificate for all hosts behind it, built-in web server and HTTP proxy
Authentication Server (optional, off by default) on a domain member computer on the safe side of the firewall, not in the DMZ authenticates users before they reach the Access Anywhere Server; only domain users, one domain at a time

All three install from the System Platform product-based installation menu, separately or together, or all on one server, which AVEVA offers for internal testing. Each must be installed locally, as remote installation is not possible. Neither the server nor the gateway can be upgraded in place: the old version is uninstalled first, after backing up any custom components. Node roles in a System Platform system: InTouch HMI or System Platform.

The server needs a 64-bit Windows Server version supported by System Platform (embedded systems are not supported), .NET Framework 4.8 or later, RDS configured, and users in the Remote Desktop Users group. Two traps: the server cannot be installed on a computer whose host name has non-English characters, and applications whose name or folder path contains & are not listed.

3. Ports and protocols

Port Protocol Process Use in the 2023 R2 SP2 documentation
443 (configurable) TCP EricomSecureGateway.exe browser to Secure Gateway, HTTPS and secure WebSocket
80 TCP Secure Gateway (HTTP proxy) redirects HTTP to HTTPS; works only when the gateway listens on 443; can be disabled
8080 (configurable) TCP AccessServer64.exe, EricomSecureGateway.exe browser or Secure Gateway to Access Anywhere Server, encrypted and unencrypted WebSocket
7433 (configurable) TCP EricomAuthenticationServer.exe Authentication Server
57111 (fixed) UDP EricomSecureGateway.exe Secure Gateway
57733 to 57735 (fixed) TCP AccessServer64.exe Access Anywhere Server

Two AVEVA pages differ on the Authentication Server: the ports table gives 7433, while the gateway configuration page gives a default port of 444.

Port 443 is also the default of the System Management Server, so a Secure Gateway installed on a node with other System Platform products conflicts with it. One of the two must move; moving the System Management Server port also means changing the System Monitor port and setting the same port on the other System Platform nodes. What the System Management Server does, and the certificates it issues, is covered in System Platform security. The gateway port is the SecuredPort value in EricomSecureGateway.Config, and the gateway does not share ports. With IIS on the same server, either IIS leaves ports 80 and 443, or the gateway moves off 443 and the HTTP redirect is disabled.

A changed server port must be typed into the browser address and set as wsport in config.js. The server installation tries to add Windows Firewall exceptions; if connections fail, port 8080 and the server program must both be allowed, and no other application on the server may use 8080. HTTPS mode, used where WebSockets are not available, requires the Secure Gateway. Plant firewall practice: firewall ports and IEC 62443 zones and conduits.

4. Licensing, as a mechanism

The InTouch 2023 R2 SP2 requirements ask for an InTouch 2012 R2 TSE (RDS) licence or newer. Each browser session uses one RDP session and one InTouch TSE licence, taken when Access Anywhere starts InTouch and released when it closes it. Per-device licences are not supported, and the System Platform installation page asks for the corresponding RDS Concurrent licence to be activated on the host. Licence types: AVEVA licensing.

5. Building the Secure Gateway

AVEVA's recommended production layout tunnels all traffic from the business network through the gateway's SSL connection in the DMZ, with every other resource behind the internal firewall. The browser-to-gateway link is always secured; whether the gateway-to-server WebSocket is encrypted depends on the Enable SSL setting. On the server, the Security page of the advanced settings turns on Use InTouch Secure Gateway and takes the gateway address.

  • Configuration Portal. HTTPS to the gateway address and port, path /admin, open only to the local Administrators group, with every logon audited. Its dashboard shows uptime, certificate status and sessions, and restarts the service.
  • Allowlists. One for client addresses and one for target hosts, in EricomSecureGateway.Config. AVEVA states the target-host list is on by default for Access Anywhere, although the sample configuration on the same page shows it set to false; the IP address of every Access Anywhere Server must be listed, or the user gets an error.
  • Session cookie. 60 minutes by default and not renewed on each page; 0 disables the timeout and should not be used.
  • High availability. Two or more gateways behind a third-party redundant load balancer, or a failover list in the client separated by semicolons; any port other than 443 is written out.

6. Certificates

Both the server and the gateway install with self-signed certificates. AVEVA notes that Chrome accepts a self-signed certificate for encrypted WebSockets, Opera warns, and Chrome OS, Safari and Firefox refuse, so a certificate from a trusted certificate authority is needed for those browsers.

For the gateway, the certificate must carry its private key (usually a .PFX; a .CER may not). It goes into the Local Computer Personal store; its thumbprint is pasted into the Security section of EricomSecureGateway.Config with CertificateFindBy set to FindByThumbprint; a service restart applies it at once. The gateway's DNS name must match the certificate name, wildcards included, or the connection fails. The dashboard's Security page also selects the certificate; there, Ignore certificate errors with a client is selected by default, and AVEVA's recommended deployment leaves every such option cleared.

For the server, the thumbprint goes into the Security tab of the Server Configuration console, or is converted with AccessNowServer32.exe /genbincert followed by the thumbprint, while the service is stopped.

7. Display and performance settings

AVEVA recommends keeping the Server Configuration console at its defaults and hiding it from end users. A service restart disconnects every session.

  • Acceleration. The server can override the clients' acceleration and quality; dynamic compression is on by default. Users choose Acceleration/Quality per session, with Very Fast / Good Quality recommended.
  • Encryption. To improve performance, AVEVA suggests setting the host's RDP encryption to Low and Access Anywhere encryption to Always, unless users also connect with plain RDP.
  • Display. Fit to browser window (default), Fit to screen or Application Resolution; resizing needs Dynamic Resolution Changes enabled in the Application Manager node properties. The minimum desktop is 800 × 600.
  • config.js. Holds defaults such as image quality, session timeout (0 by default, off), reconnect after a network drop (on) and hidden fields. By default, URL parameters override cookies, which override saved settings, which override config.js.

Setting ITAAAccessCode=0 in an application's intouch.ini hides it from the start page.

8. Known limitations and troubleshooting

The Secure Gateway known-limitations page itself refers to the Access Anywhere ReadMe; under it AVEVA covers certificate errors (use the domain name that matches the trusted certificate, not the IP address) and log files (downloaded from the portal, read with a special viewer). The server limitations AVEVA lists:

  • WindowMaker is not supported, as in any Remote Desktop session.
  • No notice when the network drops; AVEVA suggests a clock with seconds on screen.
  • TseGetClientId() and TseGetClientNodeName() always return AccessAnywhere.
  • NAD applications, and applications in folders off the local disks, are not listed while the service runs as local system.
  • Several mouse events, such as right-button and centre-click events, have no touch equivalent, and device keyboards lack F1–F12, Ctrl and Alt.
  • Closing the browser leaves the RDP session and the application running; answering No to the I/O server prompt logs the session off.

The 2023 R2 SP2 known issues add that Access Anywhere 2023b blocks access to the local drive, and that it must be removed with Remove, not Modify.

For sign-on problems, AVEVA's troubleshooting page covers pinging the gateway or server, a logon with a standard Remote Desktop Connection client, the browser and its extensions, the IP address instead of the name, then ports 443 and 8080, the running service, Remote Desktop Users membership and the certificate. AVEVA also advises one plain RDP logon per user, starting an application, before first use.

What we check first

This is TDL's practice, not an AVEVA requirement.

  • The System Platform and Access Anywhere versions, and whether a 2026 upgrade is planned, since 2026 does not include Access Anywhere.
  • Who uses it, from where, and whether they need writes or only viewing.
  • Where the Secure Gateway sits, which firewall rules reach it, and whether port 443 clashes with the System Management Server or IIS.
  • The certificate on the gateway and server, its expiry date and whether the name matches what users type.
  • The allowlists, the Authentication Server setting and its port in EricomSecureGateway.Config.
  • The TSE licence count against the number of browser sessions people open.

How TDL approaches it

TDL Industrial Automation is a System Integrator member of the AVEVA Partner Ecosystem. At SEHC, TDL maintains facility and power monitoring systems built on AVEVA System Platform, including HMI migration and extension of the SCADA. Related services: AVEVA InTouch support and upgrades and AVEVA system integrator.

Frequently asked questions

Is InTouch Access Anywhere still available in System Platform 2026?

No. The OMI 2026 release notes state that it is discontinued as of System Platform 2026, and the InTouch HMI 2026 notes say it is not on the 2026 installation media for security reasons. For browser access, the 2026 documentation describes the AVEVA web client.

Which ports does InTouch Access Anywhere use?

In the 2023 R2 SP2 documentation, browsers reach the Secure Gateway on TCP 443 and the Access Anywhere Server on TCP 8080, and the gateway also uses 8080 towards the server. The gateway's HTTP proxy listens on port 80 to redirect to HTTPS. Both 443 and 8080 can be changed.

Is the Secure Gateway required?

No, it is optional. Browsers can connect directly to the server on port 8080, typically over a VPN from outside. The gateway gives remote users one secured port from the DMZ, one certificate for all hosts behind it, and is required for HTTPS mode.

Why does the browser show a certificate warning?

The server and the Secure Gateway install with self-signed certificates, which some browsers warn about or refuse. AVEVA's fix is a trusted certificate with its private key, set by thumbprint, with the DNS name matching the certificate name.

What licence does each browser session use?

Each session uses one RDP session and one InTouch TSE licence, which is released when the session's InTouch closes. AVEVA's requirements call for an InTouch 2012 R2 TSE licence or newer and state that per-device licences are not supported.

Sources

Read 17 November 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system.

Related services:
AVEVA (Wonderware) AVEVA InTouch (Wonderware) support and upgrades