GlobalProtect App 4.1.2 Addressed Issues
GlobalProtect™ app 4.1.2 addressed issues
The following table lists the issues that are addressed in GlobalProtect™ app 4.1.2.
Fixed an issue on Windows endpoints while connecting to the GlobalProtect portal where a
Server Busymessage displayed before the user could click
OKto select a certificate and connect to the portal.
Fixed an issue where, after failing to send a logout message to the GlobalProtect gateway, the GlobalProtect app displayed the following error:
Could not connect to gateway. Please contact your IT administrator.
Fixed an issue where the GlobalProtect app displayed usernames incorrectly as follows after you enabled single sign-on (SSO) but disabled
Save User Credentialsfor the GlobalProtect portal and you enabled two-factor authentication for the GlobalProtect gateway:
Fixed an issue on macOS endpoints where the Welcome page displayed even after you selected the "Do not show this again" option.
Fixed an issue where endpoints failed to connect to a GlobalProtect portal using certificate-based authentication when FQDN resolved to an IPv6 address.
Fixed an issue where endpoints did not automatically reconnect to the GlobalProtect gateway using the cached GlobalProtect portal configuration after a prolonged network disruption if you specified
Client Certificateauthentication and set the
User-logon (Always On)(
Fixed an issue where the GlobalProtect app did not detect Dr. Web Security Space software and therefore did not include it in host information profile (HIP) reports.
Fixed an issue on Linux endpoints where end users failed to authenticate to the GlobalProtect gateway after you set the
On-Demandfor GlobalProtect apps (
) and configured RADIUS authentication with a challenge password for the GlobalProtect gateway (
Fixed an issue on Windows endpoints where the app did not display the option to
Connectagain after portal authorization failed.
Fixed an issue where endpoint users could not connect to a gateway that contained one or more UTF-8 characters.
Fixed an issue where the Universal Windows Plugin (UWP) app failed to return an error message when the wrong command (Connect) was sent from the framework during a disconnect event.
Fixed an issue where endpoints could not connect to GlobalProtect after you set the Windows System Display to Chinese and specified Chinese characters for the
Username Labelin the GlobalProtect app login page (
Fixed an issue where apps were not excluded or included as expected due to a counter that did not reset correctly.
Fixed an issue on a Linux endpoint where GlobalProtect failed to connect to an external gateway.
Fixed an issue on macOS endpoints where the GlobalProtect app could not connect to the GlobalProtect portal when the portal server certificate was signed by an intermediate certificate authority (CA) and the associated CA certificate was not installed on the endpoint. With this fix, the GlobalProtect app can connect to the portal without the intermediate CA certificate installed on the endpoint.
Fixed an issue where, after you set the
Pre-logon then On-demandfor the GlobalProtect app and an endpoint rebooted, GlobalProtect displayed a popup window prompting the user to connect (
). With this fix, users must click the system tray on their endpoint to open the GlobalProtect connect prompt after you set the
Pre-logon then On-demandand the endpoint reboots.
Fixed an issue where GlobalProtect failed to exclude split-tunnel traffic when matching an IPv6 domain if you configured the firewall to use a tunnel DNS server that did not use an offset in the Answer section of the IPv6 address record (also known as an AAAA or quad A record).
Fixed an issue on Windows endpoints where the
User overrides reached the limiterror was improperly displayed when attempting to disable the GlobalProtect app after an unknown user error.
Recommended For You
Recommended videos not found.