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.
|Application Name||Application sub-domain|
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.
- 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.
- The EAA Client connects with the enterprise application access cloud with the endpoint host name apps-example-net.go.akamai-access.com.
- The cloud forwards the connections from the EAA Client to the EAA connector via the pre-established dial-out connections.
- 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.