62 lines
3.8 KiB
Markdown
62 lines
3.8 KiB
Markdown
---
|
|
type: Addressed
|
|
product: GlobalProtect-Android
|
|
version: 6.1.11
|
|
---
|
|
|
|
## GPC-24709
|
|
|
|
Fixed an issue where iOS GlobalProtect clients intermittently failed to detect the Host ID, which caused traffic to hit unexpected security policies when Host Information Profile (HIP) based security policies were in use.
|
|
|
|
## GPC-24688
|
|
|
|
Resolved an issue where the GlobalProtect client on Android devices disconnected intermittently due to network disruption.
|
|
|
|
## GPC-24657
|
|
|
|
Resolved an issue where the GlobalProtect client on Chromebooks frequently disconnections due to StopThreads and TimeoutException when connecting to an NLB-enabled gateway.
|
|
|
|
## GPC-24024
|
|
|
|
Fixed an issue where GlobalProtect configured as Always-On did not automatically restore the connection after a network issue was resolved, even with Android settings' Always-On enabled. The system was not correctly retrieving the connect method from all configuration sources.
|
|
|
|
## GPC-22689
|
|
|
|
Fixed an issue where, when the GlobalProtect app was installed on Chromebooks, the Chromebooks were unable to connect to NLB gateway due to invalid prefix length.
|
|
|
|
## GPC-22929
|
|
|
|
Fixed an issue where Android users experienced frequent disconnections from GlobalProtect after upgrading the app to version 6.1.6.
|
|
|
|
## GPC-23778
|
|
|
|
Fixed an issue where GlobalProtect app installed on Android devices intermittently failed to send HIP reports when the device was in doze mode, resulting in the firewall removing the IP mapping for the user.
|
|
|
|
## GPC-23778
|
|
|
|
Fixed an issue where GlobalProtect app installed on Android devices intermittently failed to send HIP reports when the device was in doze mode, resulting in the firewall removing the IP mapping for the user.
|
|
|
|
## GPC-23965
|
|
|
|
Fixed an issue where Android devices running the GlobalProtect client in FIPS mode were unable to verify client certificates using OCSP (Online Certificate Status Protocol), leading to authentication failures.
|
|
|
|
## GPC-24117
|
|
|
|
Fixed an issue where Chromebooks intermittently failed to authenticate to the Prisma Access Portal when using SAML authentication. This occurred because the ACS URL would briefly open in the default browser and then immediately disappear, leading to an "authentication failed" message and an exception in the GlobalProtect logs.
|
|
|
|
## GPC-24228
|
|
|
|
Fixed an issue where Android devices running the GlobalProtect agent were unable to connect to gateways, displaying a "Could not verify the server certificate of the gateway" error. This occurred because a common code change caused the GlobalProtect agent to use the OpenSSL framework for gateway server certificate handshakes, which was unable to access certificates stored in the Android key-store.
|
|
|
|
## GPC-24937
|
|
|
|
Fixed an issue where Android mobile device users of the GlobalProtect VPN client were unable to complete SAML authentication, as they were redirected to a blank page after attempting to connect. This issue occurred regardless of whether the embedded or default browser was used for SAML authentication.
|
|
|
|
## GPC-24185
|
|
|
|
Fixed an issue where Chromebook users on GlobalProtect client version 6.1.9 could not connect to GlobalProtect gateways outside their geographical region. This occurred because when users attempted to switch gateways, a brief VPN disconnection due to higher network latency was misinterpreted by Android's Callback as a network loss. This triggered an unintended reconnection flow, prompting users for credentials and restarting the entire connection process (pre-login, login, network discovery), which resulted in the client connecting to the best available gateway instead of the user-selected gateway.
|
|
|
|
## GPC-24053
|
|
|
|
Fixed an issue where GlobalProtect clients were unable to switch their connection to a different GlobalProtect gateway, even when the desired gateway was visible and manually selected, causing clients to remain connected to their default gateway.
|