Fixes an issue where Windows devices were not able to enroll with the Zscaler App when FIPS mode was enabled for cryptography. The Zscaler App now uses FIPS-compliant cryptographic APIs in MSDN framework.
Fixes an issue where the Zscaler App periodically displayed an “Intermediate Authentication Error” upon restarting. This was due to the deletion of the Zscaler App configuration file during log rollovers.
Note: Users who experienced this with the previous version and had their App configuration file deleted will see this error even after updating to version 1.1.1. To resolve the issue, users need to log out and log in again.
Fixes an issue where the Mac OS X version of the Zscaler App did not launch automatically if users upgraded their Mac OS X devices.
Fixes an issue where if multiple users logged on and used the app on the same Mac OS X device in a short period of time, the Z-tunnel occasionally stopped functioning.
Fixes an issue where the Zscaler App was periodically unable to connect to Zscaler Enforcement Nodes (ZENs) due to errors in the App’s network adaptor DNS settings.
Fixes an issue where users were not able to connect to the Box.com Sync client if the Zscaler App was deployed in local proxy mode.
Fixes an issue where the Zscaler App periodically failed to receive regular App profile updates on non-English versions of Windows PC.
Fixes an issue where the Zscaler App was unable to apply proxy settings to PPP adaptors on Windows devices.
Fixes an issue where a raw socket error occurred periodically when users’ Mac OS X devices woke from sleep mode, preventing the Zscaler App from connecting to ZENs and leaving the device with no Internet connectivity.
Fixes an issue where the Zscaler App automatically logged out if the system keychain was locked on Mac OS X devices.
Improves Zscaler App interoperability with the Charles Proxy for users on Mac OS X devices. The App now enforces Zscaler Proxy on the Charles Proxy application.
Note: If installing the Charles Proxy after installing the Zscaler App, users must restart the Charles Proxy twice after installation so that the Zscaler App can automatically modify the Charles Proxy configuration for proxy chaining. If the Charles proxy was already installed on a user’s device before the Zscaler App is installed, the Zscaler App works seamlessly and users do not need to restart the Charles Proxy. For more details, please see How does the Zscaler App interoperate with the Charles Proxy?
In certain cases, when users uninstall the Zscaler App, users may be prompted for a system restart. If the user cancels the system restart prompt and installs the App again without restarting the system, the App will not launch. To avoid this issue, upon the system restart prompt, the user must restart the system and install the App.
Under certain conditions on Windows devices, users with the Zscaler App may receive exception alerts while logging out of their devices.
If users have Symantec AV installed on their device, the Zscaler App may not auto-update to the latest version.