Akamai​ ​​Zero Trust Client​ Mobile​ 3.1 is now available. You can update the client in the Google Play Store.

New features and improvements

Activate Threat Protection using an email address. With this release, you can enter your email address when setting up Zero Trust Client to receive a one time activation code that lets you activate Threat Protection on your device.

Full diagnostic results sharing. After running a full diagnostic of the client, you can now share the results with your administrator or save the log file on your device.

Threat Protection statistics. The mobile client now lets end users view the number of requests that are scanned and the number of requests that are blocked by the client. Users are also given graphical data to show the top domains or applications that are scanned and blocked in the past seven days and four weeks.

Activate Threat Protection via MDM solutions. You can now activate Threat Protection in Zero Trust Client by distributing the entitlement code with MDM solutions.

Proxy browser only mode support. Threat Protection now supports directing only browser traffic to the SIA proxy. In this mode, application traffic is directed to the origin and not scanned by the proxy.

TCP optimization support. EAA applications using HTTP or HTTPS protocols now support TCP optimization. To use this feature, enable TCP Optimization in Enterprise Center and contact Akamai support.

Granular Threat Protection control. Starting with client version 3.1, Threat Protection will work only if you enable Enable mobile Threat Protection in Enterprise Center.

You can now enable or disable Threat Protection independently for mobile devices, without impacting desktop client configuration. Go to Akamai Control Center > Enterprise Center > Threat Protection > Clients & Connectors > Manage and Download Clients > Configuration and enable or disable Enable mobile Threat Protection to control Threat Protection availability on mobile devices. Note that Threat Protection is disabled automatically on mobile and desktop if you disable Enable Threat Protection, regardless of the mobile setting.

Limitations

• Chrome version 127 or later users may encounter a Connection is not secure error when making HTTPS DNS queries in Incognito mode on Android. This issue occurs due to the HTTPS-First Mode in Incognitoflag being enabled by default in Chrome. To proceed to the website, users can tap Continue to site, switch to regular browsing mode, or disable the HTTPS-First Mode in Incognito flag in chrome://flags.

Supported Android versions

• Android 12 or later