GlobalProtect
Addressed Issues in GlobalProtect App 5.1
Table of Contents
Expand All
|
Collapse All
GlobalProtect Docs
-
- 10.1 & Later
- 9.1 (EoL)
-
- 6.3
- 6.2
- 6.1
- 6.0
- 5.1
-
- 6.1
- 6.0
- 5.1
-
- 6.3
- 6.2
- 6.1
- 6.0
- 5.1
Addressed Issues in GlobalProtect App 5.1
See the list of addressed issues in GlobalProtect app
5.1 for Android, iOS, Chrome, Windows, Windows 10 UWP, macOS, and Linux.
The following topic describes the issues addressed in
GlobalProtect app 5.1 for Android, iOS, Chrome, Windows, Windows
10 UWP, macOS, and Linux.
- GlobalProtect App 5.1.12 Addressed Issues
- GlobalProtect App 5.1.11 Addressed Issues
- GlobalProtect App 5.1.10 Addressed Issues
- GlobalProtect App 5.1.9 Addressed Issues (Windows, macOS, and Linux)
- GlobalProtect App 5.1.8 Addressed Issues (Windows, macOS, and Linux)
- GlobalProtect App 5.1.7 Addressed Issues (Windows, macOS, and Linux)
- GlobalProtect App 5.1.6 Addressed Issues (Windows, macOS, and Linux)
- GlobalProtect App 5.1.5 Addressed Issues (Windows, macOS, Linux, iOS, and Android)
- GlobalProtect App 5.1.4 Addressed Issues (Windows, macOS, Windows 10 UWP, Linux, Android, and iOS)
- GlobalProtect App 5.1.3 Addressed Issues (Windows and macOS)
- GlobalProtect App 5.1.1 Addressed Issues
- GlobalProtect App 5.1.0 Addressed Issues (Android Only)
GlobalProtect App 5.1.12 Addressed Issues
This release contains security-related fixes.
GlobalProtect App 5.1.11 Addressed Issues
The following table lists the issues that are addressed
in GlobalProtect app 5.1.11.
Issue ID | Description |
---|---|
GPC-15068 | A fix was made to address an OpenSSL infinite
loop vulnerability in GlobalProtect app software (CVE-2022-0778). |
GlobalProtect App 5.1.10 Addressed Issues
There are no addressed issues in GlobalProtect app 5.1.10.
GlobalProtect App 5.1.9 Addressed Issues (Windows, macOS, and Linux)
The following table lists the issues that are addressed
in GlobalProtect app 5.1.9 for Windows, macOS, and Linux.
Issue ID | Description |
---|---|
GPC-12603 | Fixed an issue where users were able to
successfully use SAML to authenticate and establish a connection
to Prisma Access but failed to connect to a manually selected Prisma
Access gateway. |
GlobalProtect App 5.1.8 Addressed Issues (Windows, macOS, and Linux)
The following table lists the issues that are addressed
in GlobalProtect app 5.1.8 for Windows, macOS, and Linux.
Issue ID | Description |
---|---|
GPC-12353 | Fixed an issue where, when the GlobalProtect
app was installed on macOS devices running Big Sur, the app was
unable to establish a connection when the Netskope Client was installed
on the system. |
GPC-12266 | Fixed an issue where, when the GlobalProtect
app was installed on Windows devices, the app was disconnected from
the tunnel and performed a network discovery after waking up from
Modern Standby mode. |
GPC-12243 | Fixed an issue where, when the gateway was
manually selected for the first time instead of the Best Available
gateway, any subsequent connections to the Best Available gateway
allowed end users to connect to the manually selected gateway rather
than the Best Available gateway. |
GPC-12202 | Fixed an issue where the Custom
Password Expiration Message (LDAP Authentication Only) notification
displayed grammatical errors when the system language was German. |
GPC-12174 | Fixed an issue where, when the GlobalProtect
app was installed on macOS devices running macOS 10.15 or 11.0,
the GlobalProtect HIP check did not detect the CrowdStrike Falcon
application, which caused the device to fail the HIP check. |
GPC-12105 | Fixed an issue where, when the GlobalProtect
app was installed on macOS devices and split tunnel was configured
based on the application, some traffic did not follow the split
tunnel configuration on applications such as Microsoft Teams. |
GPC-12104 | Fixed an issue where the GlobalProtect client
on the end user’s endpoint did not connect to the Best Available
gateway after the endpoint woke up from sleep mode. This issue occurred
when SAML authentication was used and in the auto-scaled gateway
scenario. With this fix, the GlobalProtect client can also connect
to the Best Available gateway in the auto-scaled gateway scenario. |
GPC-12050 | Fixed an issue where the GlobalProtect HIP
check did not correctly detect the Last Full Scan Time information
for the Windows Defender on Windows endpoints, which caused the
endpoints to fail the HIP check. |
GPC-12043 | Fixed an issue where, when the GlobalProtect
app was installed on Windows devices and used a smart card for client
certificate authentication, the number of prompts used between the
portals were different. |
GPC-12004 | Fixed an issue where the GlobalProtect HIP
check incorrectly detected the Anti-Malware information
for the Definition Version for Cisco Advanced
Malware Protection (AMP). |
GPC-11995 | Fixed an issue where the GlobalProtect HIP
check incorrectly detected the Anti-Malware information
for the Definition Version for Sophos Endpoint
Protection version 10.0.0. |
GPC-11932 | Fixed an issue where the GlobalProtect HIP
check incorrectly detected the Anti-Malware information
for the Last Full Scan Time for the McAfee
Total Protection Antivirus software application. |
GPC-11911 | Fixed an issue where, when the GlobalProtect
app was installed on Windows devices, the Custom Password
Expiration Message (LDAP Authentication Only) notification
is blank after you changed the message setting. |
GPC-11876 | Fixed an issue where, when the GlobalProtect
app was installed on Windows devices, the command string for pre-vpn-connect or post-vpn-connect contained
arguments with one or more whitespace characters, which caused the
built-in GlobalProtect app upgrade to fail. |
GPC-11875 | Fixed an issue where, when the GlobalProtect
app was installed on macOS devices running macOS Catalina 10.15.7,
the GlobalProtect HIP check did not detect the Anti-Malware information
for the Last Full Scan Time for the McAfee
Total Protection Antivirus software application version 4.9.2, which
caused the device to fail the HIP check. |
GPC-11865 | Fixed an issue where the GlobalProtect
Update pop-up dialog displayed grammatical errors. |
GPC-11819 | Fixed an issue where the GlobalProtect app
could not properly exclude multicast routes specified in the exclude
list. |
GPC-11784 | Fixed an issue where the GlobalProtect app
was configured with Pre-logon then On-demand mode
and if the network was changed or the network connection was lost
during pre-logon tunnel mode, the pre-logon tunnel was not able
to reconnect to the app after the machine was connected to the network. |
GPC-11749 | Fixed an issue where, when the GlobalProtect
app was installed on Linux devices, DNS resolution failed when the
app was connected on Ubuntu 20.04. |
GPC-11686 | Fixed an issue where the HIP report did
not contain the correct Last Full Scan Time information
for the AVG Internet Security software. |
GPC-11648 | Fixed an issue where, when the GlobalProtect
app was installed on macOS devices, the GlobalProtect HIP check
did not detect the Patch-Management software
for the JAMF Pro software application, which caused the device to
fail the HIP check. |
GPC-11606 | Fixed an issue where, when the GlobalProtect
app was installed on Windows devices, the GlobalProtect HIP check
did not detect the Avast Antivirus software version 20.x. After
upgrading from Antivirus software version 18.x, the GlobalProtect
HIP check did detect the Avast Antivirus software version 20.x. |
GPC-11460 | Fixed an issue where, when the GlobalProtect
app was installed on Windows devices, the GlobalProtect HIP check
did not detect the Anti-Malware information
for the Last Full Scan Time for the McAfee
Total Protection Antivirus software. |
GPC-11367 | Fixed an issue where the GlobalProtect HIP
check incorrectly detected the Anti-Malware information
for the Definition Version for Cybereason. |
GlobalProtect App 5.1.7 Addressed Issues (Windows, macOS, and Linux)
The following table lists the issues that are addressed
in GlobalProtect app 5.1.7 for Windows, macOS, and Linux.
Issue ID | Description |
---|---|
GPC-11868 | Fixed a rare issue where the PanGPS log
file was not rotated and it caused the PanGPS.log file to consume
a large amount of disk space. |
GPC-11797 | Fixed an issue where, when the GlobalProtect
app was installed on macOS Big Sur devices and split tunnel was
configured based on the application, the app was unable to connect
to applications such as Zoom. |
GPC-11781 | Fixed an issue where, when the GlobalProtect
app was installed on Windows devices, the app was disconnected from
the tunnel after the Pre-logon Tunnel Rename Timeout expired
even when users successfully authenticated to the gateway through
either SAML authentication or RADIUS for two-factor authentication. |
GPC-11723 | Fixed an issue where, after you installed
the GlobalProtect app on macOS devices using the client upgrade
prompt, a kernel panic occurred on the macOS device. |
GPC-11706 | Fixed an issue where, when the GlobalProtect
app was installed on Windows devices, the GlobalProtect tunnel could
not send traffic after the system woke up from sleep mode. |
GPC-11683 | Fixed an issue where, when the GlobalProtect
app was installed on macOS devices, the GlobalProtect virtual interface
was locally unreachable. |
GPC-11660 | Fixed an issue on the GlobalProtect agent
when the response from the gateway pre-login included the error
status and an empty message, but the GlobalProtect client was not
expected to receive the response from the pre-login with the error
status and an empty message. With this fix, the GlobalProtect client is
configured to handle the error status and the empty message response
from the gateway pre-login when the minimum version is set to TLSv1.2
in the SSL/TLS service profile. |
GPC-11656 | Fixed an issue where, after you upgraded
the GlobalProtect app to release 5.2.1 or release 5.2.2 on macOS
devices using the client upgrade prompt, a kernel panic occurred
on the macOS device. |
GPC-11649 | Fixed an issue where the GlobalProtect HIP
check did not detect Symantec Endpoint Protection 14.3 real-time
protection, which caused the device to fail the HIP check. |
GPC-11644 | Fixed an issue where the HIP report did
not contain the correct Last Full Scan Time information
for the AVG Internet Security software. |
GPC-11638 | Fixed an issue where, when the GlobalProtect
app was installed on Windows 10 devices and network connectivity
was enabled in Modern Standby, the tunnel failed to be restored
after waking up from sleep mode. |
GPC-11637 | Fixed an issue where, when the GlobalProtect
app was installed on Linux devices, the GUI version of GlobalProtect
sometimes was unresponsive (for example, when the GNOME Shell was
replaced). |
GPC-11616 | Fixed an issue where, when the GlobalProtect
app was installed on macOS devices, the GlobalProtect HIP check
did not detect Anti-Malware information for
Sophos Endpoint Protection version 10.0.0. |
GPC-11612 | Fixed an issue where, when the GlobalProtect
app was installed on Windows devices, the speed limit of the GlobalProtect
adapter was set to a maximum of 100Mbps, With this fix, the speed
limit of the GlobalProtect adapter is now set to a maximum of 2Gbps. |
GPC-11594 | Fixed an issue where, when the GlobalProtect
app was installed on Linux devices, the GUI version of GlobalProtect
hangs when multiple terminals were launched (in a multi-user target)
or when one terminal had to be launched for the GUI version to launch. |
GPC-11569 | Fixed an issue on Windows endpoints where,
if the GlobalProtect app is configured with the Pre-logon (Always
On) Connect Method with the Pre-logon Tunnel Rename Timeout value
set to -1 (or any other value) and
users disable the app and reboot their endpoint, the pre-logon tunnel
is up after they login. After the system reboots, the app is disabled
but the virtual interface is enabled. With this fix, the app and
the virtual interface are disabled after a system reboot. |
GPC-11525 | Fixed an issue where the GlobalProtect app
failed to connect to the portal or gateway in the Prisma Access
network through the proxy. |
GPC-11489 | Fixed an issue where the GlobalProtect HIP
check did not detect Patch Management information
for the Microsoft Intune management extension software. |
GPC-11478 | Fixed an issue where, when the GlobalProtect
app was installed on macOS devices and the No direct
access to local network option was enabled on the gateway,
the access route to the default gateway was not properly masked. |
GPC-11461 | Fixed an issue where, after you upgraded
and installed the GlobalProtect app, the app was unable to connect
to the gateway due to the Failed to get default route entry error message. |
GPC-11448 | Fixed an issue where the GlobalProtect app
was unable to establish a connection to the gateway because the
fully qualified domain name (FQDN) specified for the gateway mapped
to a different IP address during network discovery and pre-login.
With this fix, the app performed a network discovery again and connected
to the Best Available gateway. |
GPC-11395 | Fixed an issue where, when the GlobalProtect
app was installed on macOS devices running macOS Catalina 10.15.4,
the GlobalProtect HIP check did not detect Symantec Endpoint Protection
14.3 real-time protection, which caused the device to fail the HIP
check. |
GPC-11393 | Fixed an issue where, when the GlobalProtect
app was installed on Windows devices, the app performed a second
network discovery after gateway authentication was successful. This
issue resulted in two authentication prompts (for example, the SAML
authentication type) right after waking up from sleep mode. |
GPC-11370 | Fixed an issue where the GlobalProtect app
selected the geographically distant gateway instead of the gateway
with the faster response time. With this fix, the Best
Available gateway is now determined by the assigned
weight of the gateway. |
GPC-11349 | Fixed an issue where the GlobalProtect HIP
check incorrectly detected the Anti-Malware information
for the Engine Version, Definition
Version, and Date for the CrowdStrike
Falcon application. |
GPC-11346 | Fixed an issue where portal authentication
failed due to the authentication failure during the GlobalProtect
App Config Refresh configuration, which caused users
to be locked out of the RSA device. |
GPC-11218 | Fixed an issue where the GlobalProtect HIP
check did not detect Symantec Endpoint Protection 14.3 real-time
protection, which caused the device to fail the HIP check. |
GPC-11173 | Fixed an issue where the GlobalProtect app
was configured with On-Demand mode and continued
to stay in connecting state even when manually switching to a different
gateway failed. With this fix, the app will now display an error
message when switching to a different gateway failed. |
GPC-10954 | Fixed an issue in GlobalProtect for macOS
endpoints where installing or upgrading the package using a MDM
system such as JAMF Pro resulted in a GlobalProtect app initialization
failure. |
GPC-10934 | Fixed an issue where the original DNS suffixes
were removed from the client machine and only the DNS suffixes from
the gateway were applied. |
GPC-10831 | Fixed an issue where, when the GlobalProtect
app was installed on Windows devices, the GlobalProtect service
modified the DNS suffix system list even when the gateway pushed
an empty DNS suffix list. |
GPC-9912 | Fixed an issue where, when the GlobalProtect
app was installed on Windows devices and the pre-logon connect method
was configured, client certificate authentication failed when the
machine certificate either did not contain a Common Name (CN) or Extended
Key Usage OID value. This issue resulted in pre-logon
tunnel failure. |
GlobalProtect App 5.1.6 Addressed Issues (Windows, macOS, and Linux)
The following table lists the issues that are addressed
in GlobalProtect app 5.1.6 for Windows, macOS, and Linux.
Issue ID | Description |
---|---|
GPC-11538 | Fixed an issue where, when the GlobalProtect
app was installed on macOS devices running macOS Catalina, the GlobalProtect
service restarted after a system reboot or when users logged out
and logged in to the endpoint. |
GPC-11527 | Fixed an issue where, when the GlobalProtect
app was installed on Windows endpoints and split tunnel was configured
based on the application, handle leaks were observed by the GlobalProtect
service. |
GPC-11466 | Fixed an issue on Windows 10 endpoints where
the Active Directory Users and Computers (ADUC) application experienced
high latency when users established a GlobalProtect connection. |
GPC-11452 | Fixed an issue where when the GlobalProtect
app was enabled to Collect HIP Data in the
GlobalProtect portal agent configuration, the GlobalProtect HIP
process activated the subprocess (PanGpHipMp.exe) even when the Patch
Management category was excluded. |
GPC-11402 | Fixed an issue where, when the GlobalProtect
app was installed on Windows endpoints, the app was disconnected
from the VPN tunnel after the pre-logon tunnel grace period expired
even when users logged in to the endpoint and the pre-logon tunnel
was successfully renamed. This issue occurred when two-factor authentication
(2FA) was used. |
GPC-11392 | Fixed an issue where when the GlobalProtect
app was installed on macOS devices, the network extensions were
not loaded successfully after a system reboot. |
GPC-11365 | Fixed an issue where, when the GlobalProtect
app was installed on Linux, the GlobalProtect client hangs after
the session timed out. |
GPC-11269 | Fixed an issue where, when the GlobalProtect
app was installed on macOS devices running macOS Catalina, the app
was unable to establish a pre-logon tunnel. |
GPC-11268 | Fixed an issue where, when the GlobalProtect
app was installed on Windows endpoints, the pan_gp_event.log file
displayed the date in a different format when compared to the GlobalProtect
agent and GlobalProtect service logs. |
GPC-11257 | Fixed an issue where the GlobalProtect app
failed to connect to the portal or gateway in the Prisma Access
network when the client machine was connected only to the IPv6 network. |
GPC-11233 | Fixed an issue where the GlobalProtect app
failed to connect to the portal when the client machine was behind
the proxy and the DNS server was not able to resolve the fully qualified
domain name (FQDN) of the portal. |
GPC-11183 | Fixed an issue where the GlobalProtect HIP
check did not detect real-time protection for Traps version 4.2.2. |
GPC-11175 | Fixed an issue where the GlobalProtect driver
caused the Blue Screen of Death errors on Windows endpoints when
the third-party antivirus software was installed on the system. |
GPC-11134 | Fixed an issue where the GlobalProtect app
did not prevent users from dismissing the welcome page even when
the Allow User to Dismiss Welcome Page option
was set to No. |
GPC-11090 | Fixed an issue where, when the GlobalProtect
app was installed on Linux, users were not able to authenticate
through SAML authentication when Microsoft Azure was used as the
identity provider (ldP). |
GPC-11074 | Fixed an issue where, when the GlobalProtect
app was installed on Windows endpoints, the HIP report did not contain Anti-Malware information
for the CrowdStrike Falcon application. |
GPC-10681 | Fixed an issue where the GlobalProtect HIP
check did not detect the status as “enabled” in the Firewall setting
for the F-Secure Client Security software. |
GPC-11050 | Fixed an issue where the GlobalProtect app
tried to establish a connection without a user initiated connection
even when the connect method was set to Pre-logon then
On-demand. |
GPC-11038 | Fixed an issue where, when the GlobalProtect
app was installed on Linux, the domain name of the Linux device
was not displayed in the Domain field of
the HIP report. |
GPC-11037 | Fixed an issue where, when the GlobalProtect
app was installed on macOS endpoints and running the Blackberry
Workspaces app, the GlobalProtect app stopped running. |
GPC-10980 | Fixed an issue where the GlobalProtect app
sometimes displayed the notifications in the system tray even when
the Show System Tray Notifications option
was set to No. |
GPC-10963 | Fixed an issue where split tunnel rules
based on destination domain was applied to Windows and macOS endpoints
even with an invalid GlobalProtect license. |
GPC-10960 | Fixed an issue where, when the GlobalProtect
app was installed on Windows 10 endpoints and when users initiated
the pre-logon connection, the GlobalProtect Connect button
did not display in the Windows logon screen. |
GPC-10899 | Fixed an issue where the GlobalProtect app
was not able to establish a tunnel because the third-party software
delayed enabling the virtual adapter used by GlobalProtect. |
GPC-10454 | Fixed an issue where, when the GlobalProtect
app was installed on macOS endpoints, the HIP report included Disk
Backup information that contained invalid characters
in the version attribute for the MEGAsync
application. |
GPC-9982 | Fixed an issue, when the GlobalProtect app
was installed on macOS endpoints running macOS Catalina 10.15 or
later and HIP checks were enabled, the macOS endpoint displayed
additional pop-ups to the user when GlobalProtect requested to access
your Desktop, Documents, and Downloads folders. |
GlobalProtect App 5.1.5 Addressed Issues (Windows, macOS, Linux, iOS, and Android)
The following table lists the issues that are addressed
in GlobalProtect app 5.1.5 for Windows, macOS, Linux, iOS, and Android.
Issue ID | Description |
---|---|
GPC-11148 | Fixed an issue where, when the GlobalProtect
app was installed on Android endpoints, client certificate authentication
failed even when a valid client certificate was present. |
GPC-11101 | Fixed an issue where, when the GlobalProtect
app was installed on macOS devices running macOS Catalina 10.15.4
or later and split tunnel was configured based on the application,
file handle leaks were detected after a few weeks of usage. |
GPC-11062 | Fixed an issue where, when the GlobalProtect
app was installed on Linux, connection to the portal went through
the proxy server even when the portal address was included in the
no proxy list. |
GPC-11049 | Fixed a rare issue where the PanGPS log
file was not rotated and it caused the PanGPS.log file to consume
a large amount of disk space. |
GPC-11003 | Fixed an issue where, when the No
direct access to local network option was enabled for
split tunnel traffic on macOS Catalina 10.15.4 endpoints, some local
network traffic leaked through the physical interface. |
GPC-10969 | Fixed an issue where, when the HIP report
incorrectly displayed the Real-Time Protection status
of the Heimdal Thor Agent Anti-Malware as no instead
of yes. |
GPC-10955 | Fixed an issue where the HIP report incorrectly
displayed the Real-Time Protection status
of the ESET Antivirus as no instead of yes. |
GPC-10952 | Fixed an issue where the GlobalProtect app
was not able to authenticate to the internal gateway even when the
FQDN specified in the DHCP Option 43 Code and
associated IP address were resolved correctly. |
GPC-10933 | Fixed an issue where the GlobapProtect app
included a default route with a metric that was less than the system
default route when split tunnel based on the destination domain
was configured as inclusions. This issue caused traffic to leak through
the tunnel. |
GPC-10921 | Fixed an issue where, when the GlobalProtect
app was installed on Windows and connected to the gateway that had
split tunnel configured based on the domain and application, traffic
sent through the tunnel stopped for a few minutes even when GlobalProtect
was still connected. |
GPC-10919 | Fixed an issue where, when data was not
exchanged between the GlobalProtect service and GlobalProtect agent
for more than 2 hours because the TCP connection was not validated
and blocked. This issue caused GlobalProtect to fail. |
GPC-10890 | Fixed an issue where the Kaspersky
Endpoint Security Virus Definition Date in the GlobalProtect
HIP report did not match the actual date of the definition in the
antivirus software. |
GPC-10886 | Fixed an issue where the GlobalProtect app
failed to retrieve the client configuration that was defined in
the portal using the configuration selection criteria when the Common
Name (CN) of the certificate contained special characters. |
GPC-10879 | Fixed an issue where, when the GlobalProtect
app was installed on macOS devices running macOS Catalina 10.15.4,
the app was unable to connect to the gateway after a reboot of the
GlobalProtect client. |
GPC-10864 | Fixed an issue where the GlobalProtect app
in pre-logon mode tried to connect to the portal every five seconds
when the pre-logon cookie authentication expired. With this fix,
the app does not retry the connection to the portal until after
30 minutes. |
GPC-10820 | Fixed an issue where the GlobalProtect client
failed to refresh the portal configuration after 1 hour even though
the refresh-config-interval value was set
to 1 hour. This issue occurred when the user tunnel was established
after pre-logon with the Pre-Logon-Tunnel-Rename-Timeout value
was set to 0. |
GPC-10763 | Fixed an issue where, when the GlobalProtect
app was installed on Windows, the app did not connect to the preferred
gateway after a system reboot. |
GPC-10752 | Fixed an issue where, when the GlobalProtect
app was installed on Windows, the app retained the tunnel after
switching Windows users even when the GlobalProtect Tunnel
Preservation on User Logout value was set to 0. |
GPC-10497 | Fixed an issue where the GlobalProtect HIP
check did not correctly detect real-time protection and the Windows
Defender version on Windows endpoints, which caused the endpoints
to fail the HIP check. |
GPC-10422 | Fixed an issue where the GlobalProtect HIP
check did not detect real-time protection for Traps version 6.1.x
and 7.0.x. |
GPC-9594 | Fixed an issue where, when the gateway was
configured to include split tunnel traffic based on the destination
domain, some packets still leaked through the physical adapter. |
GlobalProtect App 5.1.4 Addressed Issues (Windows, macOS, Windows 10 UWP, Linux, Android, and iOS)
The following table lists the issues that are addressed
in GlobalProtect app 5.1.4 for Windows, Windows 10 UWP, macOS, Linux, Android,
and iOS.
Issue ID | Description |
---|---|
GPC-10843 | Fixed an issue where, when the GlobalProtect
app was installed on iOS endpoints, the app did not automatically
reconnect to the external gateway when users moved from the internal
network to the external network. |
GPC-10818 | Fixed an issue where, when the GlobalProtect
app was installed on macOS devices, the HIP process restarted multiple
times. |
GPC-10785 | Fixed an issue where the Only
with User Fingerprint option was enabled on the GlobalProtect
client even though this option was not configured on the portal. |
GPC-10745 | Fixed an issue where authentication to the
GlobalProtect gateway failed as the challenge response for multi-factor
authentication was sent to the portal and not to the gateway. This
issue occurred when the pre-logon tunnel was not renamed to the
user tunnel and the user tried to authenticate to the gateway. With
this fix, GlobalProtect authentication is now successful. |
GPC-10736 | Fixed an issue where the GlobalProtect client
on macOS endpoints did not select the client certificate when the
certificate did not have the client authentication enabled for the Extended
Key Usage. |
GPC-10682 | Fixed an issue where, when the GlobalProtect
app was installed on Linux, domain.com was sent in the HIP
profile instead of the correct domain. |
GPC-10679 | Fixed an issue where, when the GlobalProtect
app was installed on macOS, the GlobalProtect client tried to connect
to the portal after the installation when the On-Demand connect
method was defined in the property list (plist). |
GPC-10665 | Fixed an issue where, when the GlobalProtect
app was installed on Windows using Security Assertion Markup Language
(SAML) authentication and the Allow user to Sign Out
from GlobalProtect App option was set to Yes,
the username and Sign Out button were not
displayed on the app even when the Save User Credentials option
was set to No. |
GPC-10649 | Fixed an issue where, when the GlobalProtect
app was installed on Linux, GlobalProtect failed to send an XML
compliant HIP report to the firewall. |
GPC-10619 | Fixed an issue where the GlobalProtect
Refresh Connection window displayed the wrong French
characters when the system language was French. |
GPC-10591 | Fixed an issue where, when the GlobalProtect
app was installed on Windows, the app failed to download the software
from the portal when the proxy auto-configuration files were used. |
GPC-10590 | Fixed an issue where, when the GlobalProtect
app was installed on Windows UWP, the app failed to connect to the
portal or gateway when multi-factor authentication (MFA) was used. |
GPC-10580 | Fixed an issue where the GlobalProtect client
failed to authenticate to the Prisma Access gateway when multi-factor
authentication was used. |
GPC-10575 | Fixed an issue where, when the GlobalProtect
app was installed on macOS devices running macOS Catalina 10.15.4,
the app restarted multiple times and was not able to connect to
the gateway. |
GPC-10566 | Fixed an issue where, when the GlobalProtect
app was installed on Windows, the Pre-logon then On-demand connect method
did not work properly. When you set the Pre-logon Tunnel Rename
Timeout value to 0, GlobalProtect established a user
tunnel after users logged in to the endpoint instead of remaining
disconnected (On-Demand mode). |
GPC-10565 | Fixed an issue where, when the GlobalProtect
app was installed on Linux, the app did not send the complete HIP
report due to many missing patch management entries and caused parsing
issues on the gateway. |
GPC-10553 | Fixed an issue where, when the GlobalProtect
app was installed on Windows in On-Demand mode, the app was disconnected
from the tunnel, and the HIP report was not sent to the gateway
even when the gateway was selected manually after the device reboot. |
GPC-10542 | Fixed an issue where users were prompted
to enter their credentials on the GlobalProtect app 5.0.9 every
time their macOS device running macOS Catalina 10.15.3 reboots. |
GPC-10477 | Fixed an issue where the GlobalProtect HIP
check did not detect real-time protection for Traps version 7.0.1
on Windows 10 endpoints, which caused the endpoints to fail the
HIP check. |
GPC-10469 | Fixed an issue on Windows endpoints where,
if the GlobalProtect app is configured with the Pre-logon
(Always On) Connect Method and users disable the app
and reboot their endpoint, the pre-logon tunnel is up after they
login. |
GPC-10338 | Fixed an issue where, after you upgraded
the GlobalProtect app from 5.0.x release to 5.1.1 release on Windows
endpoints, the username displayed Chinese characters instead of
English characters. |
GPC-10295 | Fixed an issue where, when a split tunnel
based on the destination domain was configured on macOS Catalina
10.15.4 endpoints, all Safari-based traffic and all Mac App Store-based
traffic that were defined in the split tunnel configuration were
dropped. The same issue also occurred when you configured a split
tunnel based on the applications downloaded from the Mac App Store.
All traffic that was created for the configured applications were
dropped. With this fix, traffic defined in the split tunnel configuration
will not be dropped using Safari. |
GPC-10241 | Fixed an issue where the grace period decreased
and GlobalProtect is disconnected even after gateway authentication
was successful for the switch to the new user. |
GPC-10200 | Fixed an issue where, when the GlobalProtect
app was installed on Android devices, the app failed to reconnect
and continued to stay in connecting state. Users had to close and
launch the app to establish the connection. |
GPC-9992 | Fixed an issue where the GlobalProtect HIP
process (PanGpHip) on Windows endpoints caused high CPU usage on
the endpoint even when users remain idle. |
GlobalProtect App 5.1.3 Addressed Issues (Windows and macOS)
The following table lists the issues that are addressed
in GlobalProtect app 5.1.3 for Windows and macOS.
Issue ID | Description |
---|---|
GPC-10574 | Fixed an issue where, when the GlobalProtect
app was installed on Windows with a different language other than
English (for example, Spanish), the GlobalProtect agent was continuously
restarted. |
GPC-10535 | Fixed an issue where, after you upgraded
the GlobalProtect app from 5.0.x release to 5.1.1 release on a macOS
device, users were prompted to re-enter their password even when
the saved password was set to Yes. With this fix, users will
not be prompted to re-enter their password after the upgrade. For
GlobalProtect to access user credentials from the login keychain,
the following Keychain Pop-Up message will appear: Users are prompted to enter their password and then select Always Allow so that the Keychain Pop-Up prompt does not appear again. |
GPC-10468 | Fixed an issue where, when the GlobalProtect
app was installed on Windows, two OpenSSL DLL files in 64-bit were
not signed by a Palo Alto Networks certificate. This issue caused
a problem for some endpoint protection applications. |
GPC-10403 | Fixed an issue where the GlobalProtect app
for macOS was disabled and the Disable Timeout (min) value
expired, GlobalProtect could reconnect and user credentials were
not preserved. |
GPC-10395 | Fixed an issue where the GlobalProtect app
for macOS version 5.1.1 could not be properly installed because
the GlobalProtect service failed to launch. |
GPC-10380 | Fixed an issue where the GlobalProtect app
on macOS displayed the following error message when all the gateways
were configured as Manual Only priority:
With
this fix, the app now displays the following message:
|
GPC-10341 | Fixed an issue on Windows endpoints where,
after the endpoint woke up from sleep mode, the GlobalProtect app
was disconnected and then attempted to reconnect to the portal or
gateway. |
GPC-10311 | Fixed an issue where, when the GlobalProtect
app was installed on macOS and Windows, cookie authentication was
successful even when the wrong password was used and GlobalProtect
was still connected after users sign out of the app. With this fix,
authentication cookies are now deleted from the system when users
sign out of the app. |
GPC-10288 | Fixed an issue where, when GlobalProtect
was installed using the Windows Installer (Msiexec) with on-demand
as the connect method, GlobalProtect automatically tried to connect
to the portal. |
GPC-10261 | Fixed an issue where the GlobalProtect app
displayed the customized Captive Portal Detection Message in
the wrong format when a different language was used other than English. |
GPC-10227 | Fixed a connectivity issue where, when the
GlobalProtect app was installed for macOS Catalina, the GlobalProtect
connection was periodically lost. |
GPC-10228 | Fixed an issue where the GlobalProtect app
detected the presence of a captive portal even though it was not
present. |
GPC-10118 | Fixed a periodic issue where the GlobalProtect
tunnel failed to be restored after waking up from sleep mode. This
issue occurred when on-demand was used as the connect method. |
GPC-10024 | Fixed an issue where, after upgrading to
GlobalProtect 5.0.6, the GlobalProtect HIP check did not detect
that Symantec Endpoint Protection 14.2 real-time protection was
enabled, which caused the device to fail the HIP check. |
GPC-10190 | Fixed an issue where the GlobalProtect app
on macOS failed to find the correct certificate for authentication
to the gateway, when the object identifier (OID) was specified in
the plist. With this fix, when you provide the Key Usage OID
in the plist, the GlobalProtect app uses the correct certificate. |
GPC-9913 | Fixed an issue where the portal configuration
selection criteria failed when the certificate was signed with the
version 2 template. |
GPC-9779 | Fixed an issue that caused the GlobalProtect
app to install a default route with the same metric as the system
default route, when split-tunneling based on access route and destination
domain was enabled. This issue caused some excluded traffic to go
through the tunnel. |
GPC-9730 | Fixed an issue where GlobalProtect failed
to connect to the external gateway when the proxy was not reachable
outside of the corporate network until the GlobalProtect service
or the desktop was restarted. |
GPC-9500 | Fixed an issue in GlobalProtect for macOS
endpoints where installing or upgrading the package using a Mobile
Device Management (MDM) solution such as JAMF Pro resulted in a
GlobalProtect app initialization failure. |
GlobalProtect App 5.1.3 Addressed Issues (iOS Only)
The following table lists the issues that are addressed
in GlobalProtect app 5.1.3 for iOS.
Issue ID | Description |
---|---|
GPC-10334 | Fixed an issue with the GlobalProtect app
on iOS that occurred when two VPN profiles (one device-level VPN
profile and one per-app VPN profile) were pushed from the mobile
device management (MDM) server. This issue occurred when users initiated
the per-App VPN connection using one iOS app that was on the allow
list. The GlobalProtect app displayed the status as “Disconnected”
and the app did not respond to TAP TO CONNECT.
This prevented users from disconnecting from the per-App tunnel
and establishing a device-level VPN tunnel. |
GPC-10303 | Fixed an issue where, when GlobalProtect
was installed on iOS endpoints, the GlobalProtect app displayed
the Can’t end Background Task error
message from the GlobalProtect agent logs. This issue occurred periodically
when TAP TO CONNECT was used to establish
the GlobalProtect connection from the home screen. |
GPC-10229 | Fixed an issue where, when GlobalProtect
was installed on iOS endpoints, the GlobalProtect app failed to
perform a successful network discovery when there was a region mismatch
between the portal and the gateway. |
GPC-9135 | Fixed an issue where, when GlobalProtect
was installed on iOS devices, the GlobalProtect app did not display
a specific notification message when the GlobalProtect session has
timed out. |
GlobalProtect App 5.1.2 Addressed Issues (Android, Windows 10 UWP, and Linux)
The following table lists the issues that are addressed
in GlobalProtect app 5.1.2 for Android, Windows 10 UWP, and Linux.
Issue ID | Description |
---|---|
GPC-10444 | Fixed an issue where, when the GlobalProtect
Android app was installed on Chromebooks, the GlobalProtect app
failed to connect to the tunnel because GlobalProtect was not running. |
GPC-10370 | Fixed an issue where, when the GlobalProtect
app was installed on Android endpoints, the app hangs and the VPN
connection failed to be restored. This issue occurred when users
switch from an external network to an internal network after the Automatic
Restoration of VPN Connection Timeout option was set
to Yes. |
GPC-10362 | Fixed an issue where client certificate
authentication was failing on Android 10 devices even when the certificate
was manually selected. |
GPC-10348 | Fixed an issue where, when the GlobalProtect
app was upgraded to 5.1.1 on an Android device, the client could
no longer connect to the gateway with the custom port configuration. |
GPC-9135 | Fixed an issue where, when GlobalProtect
was installed on Android devices, the GlobalProtect app did not
display a specific notification message when the GlobalProtect session
has timed out. |
GlobalProtect App 5.1.2 Addressed Issues (iOS Only)
The following table lists the issues that are addressed
in GlobalProtect app 5.1.2 for iOS.
Issue ID | Description |
---|---|
GPC-10011 | Fixed a graphical user interface issue with
the GlobalProtect app that occurred when the device-level VPN profile
and the per-app VPN profile were pushed from the mobile device management
(MDM) server. This issue occurred when users initiated the VPN connection
from the iOS VPN settings (SettingsGeneralVPN),
and the GlobalProtect app automatically transitioned to “Connected”.
After a VPN connection was established and the app was launched,
the graphical user interface still displayed “Disconnected” even
though the VPN connection was actually running in the background. |
GPC-10173 | Fixed an issue where, when GlobalProtect
was installed for iOS and Security Assertion Markup Language (SAML)
was used to authenticate mobile users, the GlobalProtect app did
not send information about the mobile device such as the operating
system and the browser User-Agent string. |
GlobalProtect App 5.1.1 Addressed Issues
The following table lists the issues that are addressed
in GlobalProtect app 5.1.1 for Android, macOS, iOS, Windows, Windows
10 UWP, and Linux.
Issue ID | Description |
---|---|
GPC-10006 | Fixed an issue where the GlobalProtect app
was upgraded to 5.1.0 on an iOS device. This issue occurred because
the GlobalProtect was restarted during portal or gateway authentication. |
GPC-10239 | Fixed an issue where, when GlobalProtect
was installed for Android 10, the GlobalProtect app was not able
to use the client certificate for authentication. This issue occurred
when the client certificate was created with an algorithm other than
RSA. |
GPC-10260 | Fixed an issue where, when GlobalProtect
was installed for Windows UWP, the GlobalProtect app crashed when
traffic was sent through the IPSec tunnel. |
GPC-10174 | Fixed an issue where, when GlobalProtect
was installed for Android and Security Assertion Markup Language
(SAML) was used to authenticate mobile users, the GlobalProtect
app did not send the complete information about the mobile device
such as the User-Agent string for the web browser. With this fix,
the GlobalProtect app can now send the device information while
performing SAML authentication. |
GPC-10162 | Fixed an issue where, when GlobalProtect
was installed for macOS, the GlobalProtect client used the expired
certificate instead of the new certificate for portal authentication.
This issue occurred when both expired and new certificates were
installed for macOS. With this fix, the GlobalProtect client will
no longer use the expired certificate for authentication. |
GPC-10140 | Fixed an issue where, when GlobalProtect
was installed on CentOS, the GlobalProtect portal or gateway authentication
prompt did not display the customized authentication messages that
were configured in the portal configuration. With this fix, the
customized authentication messages are now displayed correctly. |
GPC-10136 | Fixed a connectivity issue where GlobalProtect
failed to reconnect to the network. This issue occurred when different
portal configurations were pushed from a mobile device management
(MDM) system one at a time. |
GPC-10110 | Fixed an issue where the GlobalProtect client
was not enabled automatically after a reboot even when the duration
timer has expired. This issue occurred when the GlobalProtect client
was disabled and your system was rebooted. With this fix, the GlobalProtect
client will now be enabled automatically even after a reboot. |
GPC-10108 | Fixed an issue where GlobalProtect crashed
on macOS devices when the Automatic Proxy Configuration was enabled. |
GPC-10100 | Fixed an issue where, when the GlobalProtect
Android app was installed on Chromebooks with On-Demand mode,
the GlobalProtect app failed to connect to the tunnel after the
device was in “sleep” mode. |
GPC-10037 | Fixed an issue where the IPSec connection
failed on a dual stack environment. This issue occurred when the
IPv6 preferred option was set to No. |
GPC-10023 | Fixed an issue where, when the GlobalProtect
Android app was installed on Chromebooks with Always On mode
and managed using the Google Admin console, the device did not reconnect
after a reboot. |
GPC-9959 | Fixed an issue where macOS users could not
connect to the GlobalProtect gateway during manual gateway selection.
This issue occurred because the portal and gateway were configured
to authenticate users through Security Assertion Markup Language
(SAML) authentication with the On-Demand connect method. With this
fix, users can now connect to the manual gateway upon the first attempt. |
GPC-9855 | Fixed an issue where the GlobalProtect App
for macOS did overwrite the local DNS search domains with the tunnel
DNS search domains. This occurred when the “Append Local Search
Domains to Tunnel DNS Suffixes (macOS Only)” app setting was set
to “No” in the portal agent configuration. With this fix, the tunnel
DNS search domains are now appended with the local DNS search domains when
the “Append Local Search Domains to Tunnel DNS Suffixes (macOS Only)” app
setting is set to “Yes” in the portal agent configuration. |
GPC-9463 | Fixed an issue where Ubuntu 19.04 did not
display the GlobalProtect system tray icon or the app could not
be launched by clicking the system tray icon. |
GPC-8743 | Fixed an issue where the GlobalProtect app
was frequently generating the pop-up dialog to request that you
change your password even when the password was not set to expire. |
GlobalProtect App 5.1.0 Addressed Issues (Android Only)
The following table lists the issues that are addressed
in GlobalProtect app 5.1.0 for Android.
Issue ID | Description |
---|---|
GPC-10099 | Fixed an issue where GlobalProtect app for
Android could not be properly connected with two-factor authentication
due to a change in the default value for the TCP Receive
Timeout (sec) option. With this fix, the default is
now 30 seconds. |