End-of-Life (EoL)

GlobalProtect App 4.0.4 Addressed Issues

The following table lists the issues that are addressed in the GlobalProtect™ app 4.0.4 release.
Issue ID
Fixed an issue where the GlobalProtect app on an Apple iPhone running iOS 11 did not connect to the gateway on the initial attempt even though authentication through 2FA for that connection attempt was successful.
Fixed an issue where iOS and Android endpoints running GlobalProtect app 4.0.3 were unable to login to GlobalProtect using SAML authentication.
Fixed an issue where Forcepoint (formerly Websense) Cloud endpoints failed to authenticate to the Forcepoint Cloud service after you installed a GlobalProtect app 3.1 or later release.
Fixed an issue in the GlobalProtect App for Universal Windows Platform (UWP) where GlobalProtect shows as connected even when the network card was disconnected or when the endpoint went in to sleep mode.
Fixed an issue in the GlobalProtect App for Universal Windows Platform (UWP) where users were incorrectly prompted to complete the certificate authentication.
Fixed an issue where administrators were unable to use JSON config files on the Google Management Console to deploy a preconfigured portal address to the GlobalProtect app on Chrome endpoints.
Fixed an issue where clicking delete ( X ) next to the username in the GlobalProtect app interface cleared the username and password but did not delete the saved cookie as expected. With this fix, the cookie is also deleted when you clear the username and password.
Fixed an issue where HIP reports did not display the drive encryption state for Check Point Endpoint Full Disk Encryption on endpoints that were running the GlobalProtect app.
Fixed an issue on Windows 10 endpoints where the GlobalProtect login prompt listed GlobalProtect Credential Provider as a single sign-on option when you used the Microsoft Remote Desktop client.

Recommended For You