Tunnel-type client-access application workflow

The workflow for securely accessing multiple applications using a tunnel application on your machine using the EAA Client as an internal host is described here.

In this example, your organization has these TCP or UDP applications hosted within your data center, with the domain-name apps.example.net:
Application Name Application sub-domain
app1 (UDP) app1.apps.example.net
app2 (TCP) app2.apps.example.net
app3 (TCP) app3.apps.example.net
app4 (TCP) app4.apps.example.net
app5 (UDP) app5.apps.example.net
app6 (UDP) app6.apps.example.net

The EAA administrator can configure a tunnel-type client-access application to provide secure access for these applications. This diagram shows the workflow involved for a tunnel-type application.

  1. Your TCP and UDP applications create connections to the internal hostname which is a wildcard application allowing all types of traffic including all subdomains on all ports. The DNS request for an internal host is intercepted by EAA Client and on board traffic via EAA Client.
  2. The EAA Client connects with the enterprise application access cloud with the endpoint host name apps-example-net.go.akamai-access.com.
  3. The cloud forwards the connections from the EAA Client to the EAA connector via the pre-established dial-out connections.
  4. The EAA connector in your data center resolves the internal hostname appX.apps.example.com of Destination 1 to find the application server IP, then performs network address translation (NAT) to establish connectivity with the respective application server.