Release notes
TrainingSupportCommunity
Back to All

Mar 23, 2020 — Enterprise Application Access, EAA Client and Device Posture updates

over 4 years ago by rskrzyck@akamai.com

Enterprise Application Access (EAA) new software release.

​Akamai​ EAA new features

  • Block Users. It allows the EAA Identity administrator to kill all existing sessions and prevent new sessions for the specified user within five to ten minutes. Blocked users can be unblocked if required. Works on ​Akamai​ identity provider and third party IdPs like Okta or Azure AD.

  • MFA Recovery code. When end-users forget to bring their 2nd-factor device this can be used as a fallback mechanism to allow validated users to access the login portal. This will work only with ​Akamai​ MFA that is part of an ​Akamai​ IdP.

  • Connector in-place upgrades. When an updated connector package is available, such as a patch to address security vulnerabilities, admins can now update the connector without having to roll out new connectors. Admins can choose the connector to apply the patch. Please note, customers are advised to use 2+ connectors per application or directory. You should upgrade one connector at a time, which will ensure disruption is minimal. Connector update packages will be tested by EAA.

    ​Akamai​ EAA Client new features

  • Device Posture New Features. With Device Posture (DP) you can improve your application security. DP collects signals about a device via the EAA Client, the EAA mobile app for iOS, or integrations with ​Enterprise Threat Protector​ (ETP) or VMware Carbon Black (ETP and VMware Carbon Black licenses required). Admins then configure rules to classify devices into low, medium, or high risk tiers or, optionally, into risk tags. Risk tiers or tags can be used as criteria along with Enterprise Application Access control rules, thus improving application security. DP includes a full set of device inventory and device posture reporting tools.

  • Mac OS X 10.15 Catalina Support. The EAA Client (including Device Posture capabilities) will be supported on Catalina, which is Apple’s newest Mac operating system.

  • Windows 10 Home Edition Support. The EAA Client (including Device Posture capabilities) will be supported on Microsoft’s Windows 10 Home Edition.

  • TunnelApp 2.0. Tunnel App 2.0 eliminates the need for admins to configure access for several applications individually, which becomes a tedious task for customers having many applications. With this new feature, admins can configure several destinations under the same client-application in tunnel mode. Multiple destination definitions can be combined, such as FQDN wildcard with *syntax, IPv4 CIDR block, protocol support for UDP, TCP or both, and port selection using range or multiple port/range. This application pooling capability saves time and reduces the chance of any error.

  • Silent Install Improvements. Admins can install or upgrade the EAA Client on many machines using software deployment/patch management solutions, such as KACE, SCCM/Intune, and JAMF. During this process, users will no longer need to click on download and configure the EAA Client.

  • Enterprise DNS. The EAA Client will intercept PTR (pointer records) and SRV (service records) queries and forward it to the enterprise’s DNS server. This supports Kerberos based authentication, which requires DNS SRV to work.

EAA and EAA Client limitations

  • No warning is displayed when you modify an existing IP based tunnel-type client-access application by adding or deleting IP addresses.

  • Silent installation of EAA Client cannot be done on a Windows 7 Enterprise (32 bit). To workaround perform a manual installation.

  • If you are using Outlook on a Windows computer, and you switch EAA Client from Wi-Fi to LAN or hotspot and back to Wi-Fi within 30 seconds, Outlook will be stuck in connecting state. The workaround is to quit Outlook and launch again.

  • If you have Oracle Virtualbox installed on Windows 7 machine, EAA Client works intermittently.

  • On-premise detection does not work if the DNS is manually modified on the machine’s network adapter’s interface. As a work-around, log out and log back into the EAA Client.

  • In Windows, on-premise detection uses DNS addresses from all interfaces to resolve hostnames. If there are any disabled interfaces, it triggers false on-premise detection. As a work-around, you should clear the DNS configuration for disabled interfaces.

  • The EAA administrator cannot customize the Enterprise DNS application URL.

  • You cannot attach an IdP to an Enterprise DNS application. It is not possible to have specific DNS servers for the same search domain for users in a particular region served by an identity provider. This can increase the latency for the users.

Device Posture limitations

  • Device Posture sends signals only when you are logged into the EAA Client mobile app or desktop app.

  • On mobile devices, if you switch out of the EAA Client app before completing registration, the application stops working.

  • Device Posture does not work if applications have a form-based user-facing or certificate-based user-facing authentication.

  • When using the EAA Client mobile app with a third-party IdP, if you experience a browser session timeout, you will see the erroneous device posture remediation message Ensure your EAA Client is installed or configured correctly. Device posture not found and is re-directed to the ​Akamai​ IdP. Users should logout of the ​Akamai​ IdP and device posture should work properly.

  • After a silent install of the EAA Client on Windows, the User ID field may be incorrect. This issue can be corrected by restarting the EAA Client or rebooting the system.

  • Device Posture anti-malware detection may display the same anti-malware signal multiple times. This does not impact functionality.

  • On macOS platform, the OS last update time field incorrectly displays the last time the OS was checked for updates instead of the last time the OS was updated. This does not impact to functionality.

  • When updating from Windows EAA Client version 1.x.x, the OSQUERY directory and files may not be deleted. They can be safely removed when running Windows EAA Client version 2.0.0.

  • If you login to an application that has Device Posture controls, using EAA Client mobile app, you maybe be denied access for the first time. Subsequent access using the retry button or accessing any other application should work.

  • If you log into the <<EAA_CLIENT_NAME> mobile app, using Safari, Device Posture might not work. The user might have to log out and then log back into the EAA Client or log in to EAA mobile app with the QR code.