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.

Issue ID	Description
GPC-6447	Fixed an issue on Windows endpoints while connecting to the GlobalProtect portal where a Server Busy message displayed before the user could click OK to select a certificate and connect to the portal.
GPC-6384	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.
GPC-6362	Fixed an issue where the GlobalProtect app displayed usernames incorrectly as follows after you enabled single sign-on (SSO) but disabled Save User Credentials for the GlobalProtect portal and you enabled two-factor authentication for the GlobalProtect gateway: When end users opened the GlobalProtect app console, the username was pre-populated in domain\username format. The GlobalProtect popup login prompt did not pre-populate the username.
GPC-6303	Fixed an issue on macOS endpoints where the Welcome page displayed even after you selected the "Do not show this again" option.
GPC-6280	Fixed an issue where endpoints failed to connect to a GlobalProtect portal using certificate-based authentication when FQDN resolved to an IPv6 address.
GPC-6257	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 Certificate authentication and set the Connect Method to User-logon (Always On) ( Network GlobalProtect Portals <portal> Agent <agent> ).
GPC-6214	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.
GPC-6209	Fixed an issue on Linux endpoints where end users failed to authenticate to the GlobalProtect gateway after you set the Connect Method to On-Demand for GlobalProtect apps ( Network GlobalProtect Portals `<portal>` Agent `<agent>` App ) and configured RADIUS authentication with a challenge password for the GlobalProtect gateway ( Network GlobalProtect Gateways `<gateway>` Authentication ).
GPC-6205	Fixed an issue on Windows endpoints where the app did not display the option to Connect again after portal authorization failed.
GPC-6199	Fixed an issue where endpoint users could not connect to a gateway that contained one or more UTF-8 characters.
GPC-6195	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.
GPC-6172	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 Label in the GlobalProtect app login page ( Network GlobalProtect Portals `<portal>` Authentication ).
GPC-6157	Fixed an issue where apps were not excluded or included as expected due to a counter that did not reset correctly.
GPC-6128	Fixed an issue on a Linux endpoint where GlobalProtect failed to connect to an external gateway.
GPC-6127	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.
GPC-6126	Fixed an issue where, after you set the Connect Method to Pre-logon then On-demand for the GlobalProtect app and an endpoint rebooted, GlobalProtect displayed a popup window prompting the user to connect ( Network GlobalProtect Portals `<portal>` Agent `<agent>` App ). With this fix, users must click the system tray on their endpoint to open the GlobalProtect connect prompt after you set the Connect Method to Pre-logon then On-demand and the endpoint reboots.
GPC-6123	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).
GPC-6084	Fixed an issue on Windows endpoints where the User overrides reached the limit error was improperly displayed when attempting to disable the GlobalProtect app after an unknown user error.

Most Popular