The following table lists the issues
that are addressed in the GlobalProtect™ app 4.0.5 release.
Fixed an issue where GlobalProtect apps did
not register their client IP addresses to the DNS server after establishing
VPN tunnel connections.
Fixed an issue where the firewall incorrectly
displayed a connected status for the VPN tunnel between a GlobalProtect
endpoint and GlobalProtect gateway even though DNS resolution of
the gateway FQDN failed.
Fixed an issue where GlobalProtect displayed
you configured a GlobalProtect gateway to use two-factor authentication
with authentication override cookies enabled and the end users trying
to access the gateway had invalid cookies (
Fixed an issue where, when connecting to a
GlobalProtect gateway with no valid certificate, GlobalProtect apps
could bypass client certificate authentication due to session reuse.
Fixed an issue where a Universal Windows Platform
(UWP) endpoint sustained a GlobalProtect VPN tunnel connection even
after the client certificate expired. With this fix, as soon as
the certificate expires, the tunnel terminates and the UWP endpoint
attempts a new tunnel connection.
Fixed an issue on Windows endpoints where the
GlobalProtect app sent a cached host information profile (HIP) report
with no host operating system or domain information after an OPSWAT
set license failure.
Fixed an issue on Mac endpoints where the GlobalProtect
app used the wrong user identifier (UID) when performing a host
information profile (HIP) check for network access control.
Fixed an issue on Windows endpoints where VPN
tunnels disconnected from GlobalProtect after the idle timeout period
because intermittent OPSWAT set license failures prevented GlobalProtect
apps from sending host information profile (HIP) reports or report
checks to the GlobalProtect gateway.