EAA Client setup overview

The EAA Client requires setup by both an EAA administrator and an IT administrator using these steps:

  1. An Enterprise Application Access (EAA) administrator enables the client in the advanced settings of the identity provider's configuration in EAA and deploys the identity provider (IdP). See Enable EAA Client in an identity provider
  2. The EAA administrator then creates a client-access application that is configured with an internal hostname. The internal hostname is the hostname of the application on the end-user’s computer. The internal hostname communicates with the actual application or application server. See Client-access applications.
  3. After an EAA administrator performs the required configuration in EAA, an end user can download the client from the EAA Login Portal and install it on their computer based on the operating system.
    Note: In most cases an IT administrator installs and distributes this software with the solution their organization uses to manage network devices. For a list of system and network requirements that apply to the client, see Requirements.
  4. After the EAA Client is installed and running, launch the configuration wizard and configure the client.
  5. After the EAA Client is running, a loopback DNS proxy is configured to capture the system DNS requests. This means that EAA Client monitors all DNS traffic to and from the end- user’s computer. The internal hostname is used to identify and intercept all traffic of interest to EAA Client. If EAA Client traffic is detected, the loopback proxy responds to these DNS requests. The loopback DNS proxy forwards requests that are not related to the EAA Client upstream in the network are forwarded for resolution.