End-of-Life (EoL)

GlobalProtect App 4.1.11 Addressed Issues

The following table lists the issues that are addressed in GlobalProtect™ app 4.1.11.
Issue ID
Description
GPC-8348
Fixed an issue on endpoints running macOS 10.13 and later releases where, if users enabled their endpoint to allow GlobalProtect to exclude traffic from the VPN tunnel (by either allowing the GlobalProtect split tunnel kernel extension to load on the endpoint or enabling Palo Alto Networks as a trusted developer), the GlobalProtect app continued to display the following error message:
Some components of the GlobalProtect App could not be launched due to Operating System Settings. This may result in some network traffic being blocked. Please contact your IT administrator.
GPC-8266
Fixed an issue on endpoints running macOS 10.13 and later releases where GlobalProtect kernel extensions were unable to load on the endpoint after it woke up from sleep mode. When this issue occurred, the GlobalProtect app displayed the following error message intermittently:
Some components of the GlobalProtect App could not be launched due to Operating System Settings. This may result in some network traffic being blocked. Please contact your IT administrator.
GPC-8174
Fixed an issue on Linux endpoints where the GlobalProtect command line interface (CLI) did not display any output for the
show - -manual-gateway
command when the output exceeded the maximum message queue size (1000 characters). With this fix, the GlobalProtect CLI splits command outputs that exceed the maximum message queue size into multiple messages.
GPC-8137
Fixed an issue where, if the GlobalProtect app was unable to connect to any external gateways after the endpoint woke up from sleep mode, it automatically connected to gateways with only the
Low
or
Lowest
Priority
when rediscovering the network.
GPC-8110
Fixed an issue in the HIP profile where GlobalProtect was unable to detect FireEye Endpoint Agent.
GPC-8109
Fixed an issue with the
Pre-logon (Always On)
Connect Method
where, if you configured GlobalProtect to authenticate users through multi-factor authentication with SAML and you set the
pre-logon-tunnel-rename-timeout
to
0
, Windows users were not automatically prompted to log in to GlobalProtect after logging in to the endpoint.
GPC-8087
Fixed an issue where Mac endpoints halted suddenly when the GlobalProtect app attempted to connect to an internal gateway.
GPC-8079
Fixed an issue with the
Pre-logon (Always On)
Connect Method
where user tunnel creation failed on Windows endpoints if you configured the following settings:
  • The GlobalProtect portal or gateway authenticates users through SAML authentication.
  • The portal and gateway generate and accept cookies for authentication override (
    Network
    GlobalProtect
    Portals
    <portal-config>
    Agent
    <agent-config>
    Authentication
    ).
  • The
    Save User Credentials
    option is set to
    Save Username Only
    (
    Network
    GlobalProtect
    Portals
    <portal-config>
    Agent
    <agent-config>
    Authentication
    ).
  • The
    Use Single Sign-On
    option is set to
    No
    (
    Network
    GlobalProtect
    Portals
    <portal-config>
    Agent
    <agent-config>
    App
    ).
GPC-8036
Fixed an issue where the GlobalProtect app for Windows 10 UWP did not send HIP reports to the firewall from domain-joined Azure AD endpoints, thereby causing these users to timeout and disconnect from GlobalProtect.
GPC-7980
Fixed an issue on Windows 10 endpoints where the GlobalProtect credential provider was unable to authenticate saved users who previously logged in with usernames in the User Principal Name (UPN) format (
username@domain.name
).
GPC-7977
Fixed an issue on Windows and Mac endpoints where, if you configured the GlobalProtect portal or gateway to authenticate users through SAML authentication, the SAML single sign-on (SSO) page appeared truncated.
GPC-7976
Fixed an issue on Mac endpoints where, if users attempted to connect to a GlobalProtect gateway manually, the GlobalProtect app did not display the gateway authentication prompt. When this issue occurred, users were unable to authenticate and connect to the gateway.
GPC-7958
Fixed an issue where, if you set the
Save User Credentials
option to
Yes
in the portal agent configuration (
Network
GlobalProtect
Portals
<portal-config>
Agent
<agent-config>
Authentication
), the GlobalProtect app was unable to save the
domain
attribute when users entered a username in the
domain\user
format. When this issue occurred, the app saved only the
user
attribute.
GPC-7905
Fixed an issue on Chromebooks where the
Reset GlobalProtect
option was greyed out from the GlobalProtect menu even though users were able to select the option.
GPC-7823
Fixed an issue where, if you configured only one external gateway for VPN access, specified the external gateway as a
Manual
only gateway (
Network
GlobalProtect
Portals
<portal-config>
Agent
<agent-config>
External
<external-gateway-config>
), and set the GlobalProtect
Connect Method
to
User-logon (Always On)
(
Network
GlobalProtect
Portals
<portal-config>
Agent
<agent-config>
App
), the GlobalProtect app connected to the external gateway automatically.
GPC-7662
Fixed an issue on Windows and Mac endpoints where the GlobalProtect app was intermittently unable to save usernames when you set the
Save User Credentials
option to
Save Username Only
in the portal agent configuration (
Network
GlobalProtect
Portals
<portal-config>
Agent
<agent-config>
Authentication
). When this issue occurred, users were unable to retrieve their cached portal configuration.
GPC-7496
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 on networks that do not support IPv6.
GPC-7449
Fixed an issue on Mac endpoints where, if you configured the GlobalProtect portal or gateway to authenticate users through multi-factor authentication with SAML, users were intermittently unable to authenticate when attempting to connect to GlobalProtect.
GPC-7422
Fixed an issue on Mac endpoints where the GlobalProtect HIP process (PanGpHip) caused high CPU usage on the endpoint after users connected to GlobalProtect.
GPC-6214
Fixed an issue in the HIP profile where GlobalProtect was unable to detect Dr. Web Security Space.

Recommended For You