Enterprise Application Access (EAA) new software release.

EAA Client versions

Akamai EAA new features

Azure SCIM Integration. You can provision users and user group memberships from Azure Active Directory (AD) to EAA Directory using the System for Cross-domain Identity Management (SCIM) 2.0.
Certificate-authentication enhancements. Perform additional certificate attribute checks while verifying a certificate as part of the IdP authentication. We support Issuer Distinguished Name, Subject Distinguished Name, and Serial Number certificate attributes.
EAA Client Forward-proxy. You can use a forward proxy between theEAA Client and EAA Cloud. The EAA Client can support both HTTP and HTTPS proxy using the underlying system settings to determine how to access the proxy. The EAA Client supports either no proxy authentication or NTLMV2 proxy authentication.
SentinelOne Anti-Malware support for Device Posture. In this release, we have added SentinelOne to the list of anti-malware products on both Windows and macOS. Customers may now detect if the SentinelOne client is active and use that as a device posture signal for any vendor list. Any vendor may be used when anti-malware is required but does not have to be a specific anti-malware product.

EAA Client versions 2.1.0 and 2.1.2 End of Service / Support - From February 28, 2022, Akamai will no longer support EAA Client versions 2.1.0 and 2.1.2. This is the last date to receive any support for these product versions. After this date, these versions are obsolete and no support will be available.
Product Migration. For customers using EAA Clientversions 2.1.0 and 2.1.2, migrating to newer EAA Client versions, will require the older EAA Client to be uninstalled before the newer EAA Client is installed. When moving to EAA Client version 2.1.0 and later, a new akamai-device-id is generated. EAA activity reports, Clients overview dashboard, Device Posture dashboard may include old akamai-device-id, resulting in inaccurate statistics until the old akamai-device-id is purged after 90 days. For more information, see Device ID (akamai-device-id) updates with EAA Client installation and upgrades.

Admins may need to clear the cache to see EAA 21.02.00 UI changes when you log in to the Akamai Control Center.
When you enable forward proxy in EAA Client and are using Safari browser, you cannot access client-access applications.
To use forward proxy on Windows 7, users need to configure Proxy Auto-Config (PAC) file manually. See EAA Client Admin Guide.
Upgrading the EAA Client to a version prior to 2.4 may cause database corruption. To avoid this you must uninstall and reinstall the EAA Client.
For a SCIM directory in EAA, the Last Synced and Last Updated values indicate the last time the directory configuration was modified.

EAA Client rejects invalid DNS SRV response.
When you use EAA Client with Akamai MFA as an MFA factor, no false error message, Failed to post code to EAA Client, please log out and log in again appears.
Connector metrics display custom domain applications data.
If you edit a certificate profile’s name, the previous name may still display on the Device Details page for up to 30 minutes.
Fixed single sign-on issue observed when Device Posture is enabled, and an OpenID Connect Application is accessed before logging into the identity provider.
EAA Client Authentication flow is fixed for the identity provider disabled with captive portal configuration.