Release notes
TrainingSupportCommunity
Back to All

Apr 5, 2019 — Enterprise Application Access and EAA Client updates

over 5 years ago by rskrzyck@akamai.com

Enterprise Application Access (EAA) new software release.

New features and performance improvements

  • Enterprise Application Access (EAA) connector migration. EAA connectors running on Ubuntu version 18.04 LTS is available for deployment. It provides increased security and better performance. Customers should migrate the connectors to run on Ubuntu 18.04 LTS before August 2019.

  • Identity capability improvements:

    • Responsive Mobile UI for identity provider (IdP). User can login to the IdP login portal from tablet or mobile device for better productivity.

    • Favorite Apps in EAA Login Portal. You can customize EAA Login Portal by moving the frequently accessed applications to the favorites section of the IdP login portal.

    • OIDC/Oauth 2.0 for Internal Apps. OpenID Connect 1.0 (OIDC) is a federated protocol that provides an identity layer that is built upon OAuth 2.0. It enables clients (applications or user agents, relying party) to verify the identity of the end user based on the authentication performed by the authorization server, or OpenID provider.

    • Chase Referral Support for Active Directory (AD). Organizations can have multiple Active Directory (AD) domains for different geographical regions. To sync all of the users in all groups, EAA has the global catalog server option.

    • Dashboard 2.0 Reports. EAA administrator can drill down to obtain detailed reports by clicking the hyperlinks on the dashboard.

    • Access the EAA Management Portal from ​Akamai Control Center​. Enterprise Application Access (EAA) Management Portal is accessible from the ​Akamai Control Center​. You can manage groups and properties for your ​Akamai​ accounts and monitor, configure, resolve, and plan your products from the menu.

    • Login Portal languages. An EAA administrator can customize the text that appears in the Login Portal’s welcome banner, page title, legal disclaimer, username hint, password change label and new user signup label field. EAA supports text in English, German, French, Spanish, Japanese, Italian and Chinese.

    • Customize the Login Portal tab name in the browser. User can change the browser tab name for the Login Portal. The default tab name for the login portal of the IdP is Login in the browser window.

  • EAA Client Connector Enhancements:

    • Support for Apple Mojave OS. The EAA Client Connector runs on these operating systems (OS):

      • Microsoft Windows 7 or Windows 10 Enterprise (32-bit and 64-bit)
      • Apple macOS 10.11 El Capitan, macOS 10.12 Sierra, 10.13 High Sierra, or 10.14 Mojave

    • See network diagnostics in client skin. The Run Diagnostics function examines the status of the installation, connectivity, components, and configuration downloads from the EAA solution. Green check marks indicate success and red X marks indicate failure.

    • Save logs to local hard disk. EAA Client Connector allows the end user to save and also send a zipped version of the logs, device ID and version to the EAA administrator. The administrator can provide this information to ​Akamai​ support for troubleshooting.

    • Changes to configuration on-boarding. The configuration is manual to enhance security posture of the client.

    • Display client logs in Admin portal. The admin can click on View Logs to view all of the log types: INFO, DEBUG, and ERROR. To check a specific type of log, click Level and select the log types you want to view.

    • Common Interface File System (CIFS) Support. CIFS is supported in EAA Client Connector.

    • Self-Upgrade of EAA Client Connector. Users can check for updates in the client, and perform a self-upgrade if necessary.

Bug Fixes

  • Italian Email Notification enhancements. Added Italian language support email and SMS MFA templates.

  • Discovered apps performance improvements. Discovered apps page in client dashboard has faster performance.

  • Active Directory (AD) Group Search Improvement. AD group search performance is improved when admin searches for groups. Admins see faster results with less latency.

  • Software Design Kit (SDK) Improvements. Added all application related functionality, IdP deployment capability to the SDK.

  • Support for mixed IP environments. This release adds better support for both IPv4 and IPv6 environments. EAA Client Connector will fallback to IPv4, if IPv6 support is incorrectly configured in user network.

Known limitations

  • When upgrading EAA Client Connector from beta to LA release (retaining the configuration), IdP page shows reconfigure as an option because IdP tokens have changed. It is a benign condition. This status will remain on the IdP page until the user clicks the reconfigure option and gets the new IdP token added for the LA release. This does not affect new seeding or configuration.

  • When client is in disconnected state, status of the IdP page on first refresh incorrectly says client is not installed, the second refresh displays the right status that client is not running.

  • When configuring the EAA Client Connector for the first time, clicking the diagnostics button may result in a configuration error while the TCP apps being configured. This is because EAA Client Connector diagnostics does not distinguish TCP with tunnel apps. As soon as all the tcp apps configured are started, all checks in diagnostics will become green. This only affects first time configuration.

  • Changing MFA Helpdesk email: When the helpdesk email option is changed in System - Settings (for MFA), only the default IdP prompts to redeploy. Any other IdP’s that have MFA enabled do not prompt Ready for Deployment. These can be deployed manually, but this may cause confusion for customers.

  • IdP Configuring max session duration: When max session duration is configured to be less than Idle expiry – IdP deployment fails.

  • IdP portal rendering issues: When logged in user resizes the IdP portal browser window, users may experience these issues: (a) EAA client download button will disappear; (b) MFA registration buttons won’t work; (c) User account actions such as ‘account settings, logout and change password’ will come as mobile browser.

  • EAA Client Connector upgrade on Windows 7 or Windows 10: When trying to reinstall EAA Client Connector on an existing installation, upgrade may fail in cases with this error: There has been an error. Could not kill process with pid [pid]. This is due to Windows OS locking the old processes. Workaround is to try again and re-run the upgrade of EAA Client Connector.

  • EAA Client Connector and IdP interaction: If the user closes the auth form by mistake during the authentication, user then has click re-authenticate/sync button.

  • IdP default POP and configuration: When admin changes POP of the default IdP instance, corresponding directory configuration won’t be deployed the newly selected IdP POP. Customer admins can reach out ​Akamai​ support to correct the problem.

  • EAA Client Connector does not support domains that use non-ASCII characters.

  • EAA Client Connector intercepts traffic based on fully qualified domain names (FQDN) only.

  • EAA Client Connector user interface language only supports English.

  • EAA Client Connector may not work with forward proxies in the network.

  • EAA Client Connector does not support Kerberos authentication.

  • EAA Client Connector does not support Service Records (SRV) in a Domain Name System (DNS). Applications like Microsoft Exchange, which rely on this, require a VPN or corporate network.The EAA Client Connector can then access the application.

  • EAA Client Connector does not support Extensible Messaging and Presence Protocol (XMPP) in DNS. The Pidgin application, which relies on this, requires a VPN or corporate network for this initial setup. The EAA Client Connector can then access the application.

  • File transfer protocol (FTP) does not work with EAA Client Connector. To work around this issue, modify the FTP server settings to select an external IP address of the firewall (or server external IP address). Provide an unroutable loopback IP like 127.50.100.1. Now the FTP client can use the server hostname instead of IP.

  • Client-access applications are not supported with docker-based connectors.

  • EAA Client Connector is not supported on macOS 10.13 High Sierra with case- sensitive Apple File System (APFS).

  • When an ACL rule is set to deny a user access to a client-access application, and if that user tries to access the application, the EAA Client Connector will only update the denied user’s eeaclient.log with a generic 403 error message.

  • For tunnel-type client-access applications, if the application server is running multiple applications on the same IP address, same port, and using the same protocol, the access control list (ACL) rules might not be applied reliably and there is a vulnerability.

  • VoIP applications like Skype have not been tested on EAA Client Connector and may have performance issues.

  • EAA Client Connector will not work when Nmap Project’s packet sniffing (and sending) library (NPCAP) loopback adaptor is installed on a Windows machine.

  • The macOS firewall rule allowing EAA Client Connector traffic may be removed on Mac computers. When the machine reboots, users need to click Allow when prompted to accept incoming connections.

  • When you first install the EAA Client Connector on Windows, a Windows Security dialog prompts to install the network TAP driver. Click Install. Silent installation may be impacted by this limitation. To resolve the issue, deploy the TAP driver certificate before the silent install command line.

  • EAA Client Connector zipped log files contains an empty akamai_dpclient.log. It can be ignored by user.