GlobalProtect App 4.0.3 Addressed Issues
The following table lists the issues that are addressed in the GlobalProtect™ app 4.0.3 release.
Fixed an issue where user authentication to a GlobalProtect portal failed after an endpoint connected through the pre-logon method because GlobalProtect did not change the session username from
pre-logonto the username of the user.
Fixed an issue in the GlobalProtect app interface where clicking
Connectdisplayed the misleading message
Disconnectedfor five to six seconds before the message changed to
Connectingand finally to
Connected. With this fix, the interface does not display
Disconnectedwhen the GlobalProtect app initiates a connection.
A security-related fix was made to prevent an image path execution hijacking vulnerability on GlobalProtect apps (CVE-2017-15870).
Fixed an issue where the firewall frequently, randomly disconnected end users from GlobalProtect because socket closures terminated SSL sessions.
Fixed an issue where GlobalProtect gateway connections failed if you configured the GlobalProtect portal to enable users to manually connect with gateways on a port number (
Fixed an issue where Opswat initialization failure brought down the VPN tunnel because the GlobalProtect app did not send a host information profile (HIP) report to the GlobalProtect gateway. with this fix, the GlobalProtect app sends its cached HIP report if Opswat initialization fails.
As an enhancement to support the KEXT loading change introduced in macOS 10.13, you can now install GlobalProtect app 4.0.3 and later releases on endpoints running macOS 10.13.
Fixed an issue where the GlobalProtect app displayed the login passcodes for GlobalProtect clients as cleartext in the GlobalProtect client logs and in the memory space for the PANGPA process. With this fix, the GlobalProtect app does not display login passcodes in the GlobalProtect client logs and clears the passcode field in memory after use.
Fixed an issue where end users on Windows 10 endpoints could not use the user principal name (UPN) format to log in through a GlobalProtect tile if you configured single sign-on (SSO) wrapping for third-party credential providers.
Fixed an issue where host information profile (HIP) reports displayed incorrect dates for the antivirus software on GlobalProtect clients.
Fixed an issue where GlobalProtect clients sent previously used One-Time Passwords (OTPs) to the GlobalProtect gateway even when two-factor authentication was enabled for app configurations on the GlobalProtect portal (
). With this fix, GlobalProtect clients do not reuse OTP passwords.
Fixed an issue where GlobalProtect connections failed after you changed the connection settings to use an external gateway without a proxy server instead of an internal gateway with a proxy server.
Fixed an issue where, when the GlobalProtect internal gateway and GlobalProtect portal were in different regions, the GlobalProtect app displayed the message
Your device cannot connect to GlobalProtect due to a network issueeven though users could successfully connect to the gateway. With this fix, the GlobalProtect app no longer displays that message when users connect to the gateway.
Fixed an issue where iOS endpoints had slow file and data transfer rates through a GlobalProtect VPN tunnel.
Fixed an issue where the firewall sent URL-encoded passwords to a remote authentication server if end users chose to
Cancelauthentication to a GlobalProtect gateway and you configured GlobalProtect apps to
Save User Credentials(
Fixed an issue where the Japanese language version of the GlobalProtect app interface displayed the incorrect text for the
Fixed an issue where mobile endpoints running Windows 10 Universal Windows Platform (UWP) did not connect to the GlobalProtect portal and displayed one of the following error messages:
client cert invalidor
no certificate found.
Fixed an issue where GlobalProtect apps did not accurately enforce the Login Lifetime (
Fixed an issue on laptops running Windows 10 with BitLocker encryption where GlobalProtect briefly displayed the date and time every 30 seconds in the Windows login prompt.
Fixed an issue where the GlobalProtect app did not collect Missing Patches information about GlobalProtect clients as specified in the host information profile (
Fixed an issue where GlobalProtect remained connected to endpoints after end users removed the USB smart card even if you set Retain Connection on Smart Card Removal to No for GlobalProtect apps (
Fixed an issue where the German language version of the default warning message for password expiration had a typo.
Fixed an issue where, after rebooting, Windows laptops did not display the list of GlobalProtect gateways that end users could manually select for connecting through certificate-based authentication.
Fixed an issue where, instead of notifying the end user when gateway authentication failed due to an incorrect password, GlobalProtect displayed the Authentication Message (
) and prompted the user to re-enter the password. With this fix, GlobalProtect displays
Authentication Failedand then the
Authentication Messageif the user enters the wrong password.
Fixed an issue where the GlobalProtect app on Mac OS X endpoints failed to set the primary IPv6 DNS address to the virtual adapter.
Fixed an issue on Mac endpoints where the GlobalProtect app disconnected and did not recover the default route for a VPN split tunnel after the endpoints came out of sleep mode or moved between access points.
Recommended For You
Recommended videos not found.