GlobalProtect App 4.1.5 Addressed Issues
The following table lists the issues that are addressed in GlobalProtect™ app 4.1.5.
Fixed an issue where the GlobalProtect app retained DNS servers associated with gateways to which the app had previously connected.
Fixed an issue on Microsoft Surface endpoints where GlobalProtect could not connect to local gateways when the endpoint was coming out of a sleep state due to the PANGPS process halting abruptly.
Fixed an issue on Windows 10 endpoints where GlobalProtect app 4.1.4 failed to uninstall successfully if Visual C++ redistributables were not installed on the endpoint.
Fixed an issue on Microsoft Surface endpoints where GlobalProtect could not connect to local gateways when the endpoint was coming out of a sleep state due to a mismatch in states for the PANGPS and PANGPA services.
Fixed an issue where SAML login can fail when you use a load balancer, as the load balancer can resolve the portal FQDN into multiple IP addresses.
Fixed an issue where GlobalProtect displayed a large notification when an authentication or server access issue occurred. Now, GlobalProtect displays an updated error message which describes the issue and instructs the user to contact their IT helpdesk from the main panel (when open) or the login dialog (when the main panel is closed).
Fixed an issue on macOS endpoints where the GlobalProtect app failed to uninstall cleanly, which resulted in network connectivity issues.
Fixed an issue on Google Pixel endpoints running Android 9.0 where the GlobalProtect app terminated abruptly due to a system API call.
Fixed a SAML authentication issue where users could not log in to the GlobalProtect portal when you used DNS load balancing to load-share multiple portals.
Fixed an issue on macOS endpoints where HIP collection failed due to a PanGpHIP crash on the GlobalProtect app.
Fixed an issue on Linux endpoints where, after establishing the GlobalProtect connection, the local DNS servers were removed from the /etc/resolv.conf file because the GlobalProtect adapter did not have an assigned DNS server.
Fixed an issue on Windows 10 endpoints where the GlobalProtect Credential Provider was unable to wrap third-party credential providers for single sign-on (SSO).
Fixed an issue on Android endpoints where the list of GlobalProtect gateways did not populate on the GlobalProtect app for user selection. This issue occurred when the GlobalProtect portal was configured only with manual-only external gateways.
Fixed an issue on Linux endpoints where the GlobalProtect app prompted end users to enter their credentials in succession despite entering correct credentials. This issue occurred after the end user attempted to connect to an alternate manual gateway configured with the User-logon (Always On) connect method.
Fixed an issue on Android endpoints where users could establish a GlobalProtect connection through the GlobalProtect app without a GlobalProtect license. This issue occurred when users authenticated to the GlobalProtect portal and gateway using SAML single sign-on (SSO).
Recommended For You
Recommended videos not found.