Jul 26, 2019 — EAA Client updates

Enterprise Application Access (EAA) new software release.

​Akamai​ EAA Client New features

  • IPv4-based access for tunnel applications. EAA Client extends zero trust access functionality to access applications defined by IPv4 addresses.

  • Captive portal detection. EAA Client detects the presence of captive portals and gracefully reconnects when network connectivity is established. See Captive portal support in EAA Client Admin Guide.

  • On-premises network detection. Based on network policies configured by an EAA administrator, EAA Client can detect if a user is on-premises. In this situation, the client allows direct access to enterprise applications that bypass access through the proxy.

Akamai EAA Client Usability Improvements

  • Client menu simplification. The EAA Client menu is now more intuitive and includes tooltips to guide end users. The Setting menu provides improved logging capabilities. New settings names and menu organization allows users to complete advanced operations more easily. These operations include checking diagnostics, viewing the network type and status, accessing the synchronize and reset functions, and downloading the latest version of the client software.

EAA Client Limitations

  • After you upgrade to the latest version of EAA Client (version 1.3.X), you cannot downgrade to the previous version (version 1.2.X). Rolling back to version 1.2.X requires that you uninstall version 1.3.X and reinstall version 1.2.X of the EAA Client.

  • You will not be able to configure the EAA Client from the IdP login portal on a Microsoft EDGE browser. Use an alternative browser like Chrome.

  • When connecting to a captive portal on a Mac, the captive portal may block all outgoing traffic. In this situation, the client shows that the network type is NONE. EAA Client cannot reliably detect whether the end user is on a public network or a captive portal.

  • When the user is connected to both trusted and untrusted networks on two different networks, EAA Client inconsistently detects whether the user is on a trusted network or a public network.

  • The identity provider (IdP) name may not appear in the EAA Client. To resolve this issue, quit and restart the EAA Client.

  • On macOS, clicking logout in the client may cause all menu options to gray out. To resolve this issue, open the Activity Monitor application in the Utilities folder of the Mac. Select EAA Client and then click the quit icon. In the dialog that appears, select Force Quit.

  • When adding multiple IPv4 addresses to a “Tunnel” type application, you are limited to adding a maximum of 214 IPv4 addresses to an application. If you have more than 214 addresses, you must add additional tunnel applications as needed.

Limitations for Enterprise Application Access

  • When accessing an application, an IdP session is not saved between browser tabs on these versions of Microsoft Edge and Internet Explorer: Microsoft EdgeHTML: 17.17134, Microsoft Edge: 42.17134.10, IE: 11.590.17143. If a user opens a new tab in these browsers, they are prompted to enter their Login Portal credentials again.

  • When using the Login Portal with a Microsoft Edge or Internet Explorer browser, a user may experience multiple UI issues such as long loading times, the favorite icon (heart symbol) not appearing, and more.

  • If you open the print dialog in a remote desktop protocol (RDP) server session and you then click the desktop before making your selections, the dialog may disappear. To workaround this issue, you must open the print dialog again.

  • If only DNS server settings are changed in network interfaces, on-premise network monitoring may not detect that the network type has changed from or to a trusted network.

  • When there are multiple data centers that have the same network configuration, connectors assigned to these data centers should not be associated to a single tunnel application.