GlobalProtect App 4.1.7 Addressed Issues
The following table lists the issues that are addressed in GlobalProtect™ app 4.1.7.
Fixed an issue where the GlobalProtect app for Chrome displayed the incorrect connection status after users closed and then reopened the app.
Fixed an issue on Windows 10 endpoints where, if you configured the GlobalProtect app to wrap third-party credentials, users were unable to change expired passwords using the GlobalProtect Credential Provider.
Fixed an issue on Windows 10 endpoints where, if a GlobalProtect user connected to a gateway with split tunneling and then switched to a gateway without split tunneling, the split tunnel logic from the original gateway persisted on the GlobalProtect app. This issue caused users to lose access to applications, as network traffic incorrectly continued to bypass the VPN tunnel.
Fixed an issue on GlobalProtect app 4.1.6 where, if you configured a split tunnel to exclude traffic from the VPN tunnel based on access routes, GlobalProtect incorrectly installed all exclude access routes with a
/32subnet mask instead of the configured subnet masks.
Fixed an issue where the GlobalProtect app for macOS was not being upgraded transparently because the refresh configuration was not triggered properly.
Fixed an issue where the GlobalProtect app could not connect to external gateways if you specified a
Source Regionother than
Anyin the external gateway configuration (
). This issue occurred when you configured all external gateways as manual-only gateways and set the GlobalProtect
User-logon (Always On)in the portal agent configuration (
Fixed an issue on Windows endpoints where, if you configured GlobalProtect with the SAML authentication method, the app displayed a
Portal Not Founderror message after users restarted their endpoints.
Fixed an issue on Windows 10 endpoints where, if you configured GlobalProtect with the pre-logon connect method, the GlobalProtect Credential Provider displayed incorrect translations for the pre-logon connection status in all non-English languages.
Fixed an issue with the UWP plugin for Windows 10 endpoints which caused GlobalProtect to report an
Fixed an issue on Windows endpoints where gateway authentication failed when the network was unreachable during tunnel restoration.
Fixed an issue where, if you configured a split tunnel to exclude application traffic based on the application process name, application traffic destined for UDP port 9000 was incorrectly sent through the VPN tunnel.
Fixed an issue on Windows endpoints where the GlobalProtect app displayed the Welcome page only after connecting to a GlobalProtect gateway instead of after connecting to the GlobalProtect portal.
Fixed an issue where the GlobalProtect app incorrectly saved usernames when you set the
Save User Credentialsoption to
Noin the portal agent configuration (
Fixed an issue where PanGPA halted unexpectedly when the endpoint was brought back from sleep and GlobalProtect switched from an internal to an external gateway.
Fixed an issue with pre-logon where GlobalProtect prompted the user to authenticate to both the portal and gateway when the network was unavailable when the user logged into the endpoint.
Fixed an issue on Windows 7 endpoints where, if you configured the options to
Enforce GlobalProtect Connection for Network Accessand
Display Traffic Blocking Notification Message(
), the GlobalProtect app intermittently displayed the
Captive Portal Detectedmessage instead of the specified traffic blocking notification message even though a captive portal was not detected.
Fixed an issue on Windows 10 endpoints where the domain name was pre-populated on the Windows login screen even when users selected the
Otheruser login option. This issue occurred because the GlobalProtect credential provider was automatically set as the default credential provider on Windows 10 endpoints.
Fixed an issue on Windows 10 endpoints where GlobalProtect displayed password expiry notification messages as toast notifications. With this fix, password expiry notification messages now appear as notification balloons in the system tray. If multiple GlobalProtect notifications trigger at the same time, the notification balloon also displays a
More Notificationslink, which enables users to view a summary list of the notifications.
Fixed an issue where, if GlobalProtect was connected to an internal network with no internal gateways, the GlobalProtect app intermittently displayed the
Connectingstatus even though network discovery was complete.
Fixed an issue on Windows endpoints where the GlobalProtect app misidentified Kapersky Endpoint Security as Kapersky Antiphishing and indicated an incorrect version number in the Host Profile.
Fixed an issue where the GlobalProtect app did not retain the domain name from
Usernameinputs in the
domain\usernameformat following unsuccessful GlobalProtect authentication attempts.
Fixed an issue where Windows activation failed upon system reboot because the Windows license was getting deleted when you enabled HIP checks.
Fixed an issue on Linux endpoints where, after users established the GlobalProtect connection, network traffic was sent through the default route of the physical adapter instead of the default tunnel route. This issue occurred because the default route of the physical adapter had a lower metric and therefore higher priority than the default tunnel route.
Fixed an issue where, if you set the
Save User Credentialsoption to
Save Username Onlyin the portal agent configuration (
), the GlobalProtect app incorrectly placed the cursor in the
Usernamefield instead of the
Passwordfield when users were prompted to enter their passwords for portal or gateway authentication.
Recommended For You
Recommended videos not found.