End-of-Life (EoL)

GlobalProtect App 4.0.2 Addressed Issues

The following table lists the issues that are addressed in the GlobalProtect™ app 4.0.2 release.
Issue ID
Description
GPC-4135
Fixed an issue where the GlobalProtect app could not connect with a GlobalProtect gateway that was configured to use a SAML-based authentication profile and to use an SSL/TLS Service profile with TLS 1.2 as the minimum version (
Network
GlobalProtect
Gateways
).
GPC-4131
Fixed an issue where the GlobalProtect app could not connect if the GlobalProtect portal and gateway used different certificate profiles.
GPC-4123
Fixed an issue where, after you configured two-factor authentication using One-Time Passwords (OTPs), the GlobalProtect gateway displayed an authentication failure message to end users even though they authenticated successfully.
GPC-4092
Fixed an issue where the GlobalProtect app did not send Host Information Profile (HIP) reports to internal GlobalProtect gateways; PanGPS logs displayed the message
No hip report thread is created
.
GPC-4089
Fixed an issue on iOS endpoints where, the first time the user selected
Auto Discovery
after disconnecting from the GlobalProtect portal, GlobalProtect reconnected the user without prompting for login credentials even when you set
Save User Credentials
to
No
(
Network
GlobalProtect
Portals
<GlobalProtect-portal-config>
Authentication
).
GPC-4071
Fixed an issue where the GlobalProtect app collected incorrect Host Information Profile (HIP) data for the latest AVG™ Antivirus software.
GPC-4069
Fixed an issue where the GlobalProtect app running on an endpoint device with the Mac OS prevented users from authenticating through certificates stored on a smart card or PIV card.
GPC-4068
Fixed an issue where HIP reports did not display SolarWinds N-able Security Manager – AV Defender™ software.
GPC-4065
Fixed an issue where GlobalProtect did not correctly restore DNS settings if you configured the GlobalProtect portal to Update DNS Setting at Connect (
Network
GlobalProtect
Portals
<portal-configuration>
Agent
<agent-configuration>
App
App Configurations
).
GPC-4064
Fixed an issue where the GlobalProtect HIP check did not identify BitDefender for Mac version 5.2.1.1.
GPC-4062
Fixed an issue where connecting to GlobalProtect through a Wi-Fi adapter that contained Chinese and some special characters caused the GlobalProtect service (PanGPS) to stop running.
GPC-4059
Fixed an issue where the firewall blocked IPv6 loopback traffic if GlobalProtect was not connected and you configured the GlobalProtect portal app to Enforce GlobalProtect Connection for Network Access (
Network
GlobalProtect
Portals
<portal-configuration>
Agent
App
).
GPC-4058
Fixed an issue where the GlobalProtect app running on an endpoint device with the Mac operating system (OS) did not detect CylancePROTECT® v2.0 threat protection software.
GPC-4053
Fixed an issue where upgrading the GlobalProtect app through MSI Command Center removed the wrap-cp-guid registry entry.
GPC-4047
Fixed an issue where the GlobalProtect app could not connect to the portal or gateway when using only certificates for authentication.
GPC-4044
Fixed an issue where end users could not reconnect a Chromebook device to GlobalProtect after manually disconnecting; GlobalProtect repeatedly prompted for a username and password regardless of the credentials that users entered.
GPC-4015
Fixed an issue where GlobalProtect single sign-on (SSO) failed for end users who entered passwords containing special characters such as the euro sign (€).
GPC-4008
Fixed an issue where the GlobalProtect app failed to authenticate to a RADIUS one-time password (OTP) server if that server required the app to send a username without the associated domain for logins and if you configured the app to Use Single Sign-on (
Network
GlobalProtect
Portals
<portal-configuration>
Agent
<agent-configuration>
App
). The issue occurred because the app sent only the username for the first login but sent the domain\username for subsequent logins.
GPC-4004
Fixed an issue where the HIP module of the GlobalProtect app consumed too much CPU time while evaluating the LANDESK vulscan.exe application.
GPC-3999
Fixed an issue where, when a user tried to establish an RDP connection to (or switched Windows users on) an endpoint that had an active GlobalProtect tunnel, the GlobalProtect tunnel on the remote machine was disconnected even though you configured a positive User Switch Tunnel Rename Timeout value (
Network
GlobalProtect
Portal
<portal-configuration>
Agent
App
).
GPC-3989
Fixed an issue where the GlobalProtect app stopped running if you did not specify a gateway Name in the portal configuration (
Network
GlobalProtect
Portals
<portal-configuration>
Agent
Internal/External
<gateway-configuration>
.
GPC-3986
Fixed an issue where the tray icon for the GlobalProtect app did not display after you restarted Microsoft Windows Explorer.
GPC-3909
Fixed an issue where the GlobalProtect app could not use a client-side certificate stored on the Gemalto SafeNet eToken for client certificate authentication.
GPC-3884
Fixed an issue with Single Sign-On (SSO) on Windows 8.1 where endpoint users had to click the GlobalProtect app sign-in icon multiple times to select it.
GPC-3883
Fixed an issue where HIP profiles did not correctly detect the
Virus Definition Version
and
Last Scan Time
for CylanceProtect.
GPC-3857
Fixed an issue where, if you Enforce GlobalProtect for Network Access in the GlobalProtect portal configuration (
Network
GlobalProtect
Portals
<GlobalProtect-portal-config>
Agent
<agent-config>
App
App Configurations
), the GlobalProtect app blocked re-transmission of client DHCP requests with the same Transaction ID as the initial request (such as when re-transmitting the request after failing to receive a response from the server to the initial request). This issue was encountered only in unstable or other environments that require more than one DHCP request before receiving a response from the server.
GPC-3545
Fixed an issue where HIP profiles did not correctly evaluate the
Last Full Scan Time
for Norton Security antivirus software.
GPC-3431
Fixed an issue where the GlobalProtect app on a Windows endpoint could not reconnect to GlobalProtect after the endpoint experienced a crash or hard reboot if you required endpoints to
Update DNS Settings at Connect
(
Network
GlobalProtect
Portals
<GlobalProtect-portal-config>
Agent
<agent-config>
App
App Configurations
). This issue occurred because the app could not restore the automatic DNS configuration.
GPC-3377
Fixed an issue where GlobalProtect single-sign on (SSO) failed when the user logged on to an endpoint using Windows Remote Desktop (RDP).

Recommended For You