Add GP 6.1 addressed issues
This commit is contained in:
@@ -0,0 +1,41 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect-iOS
|
||||
version: 6.1.0
|
||||
---
|
||||
|
||||
## GPC-19030
|
||||
|
||||
Fixed an issue where GlobalProtect 6.1.0 on iOS 17 cannot connect gateways successfully.
|
||||
|
||||
## GPC-18672
|
||||
|
||||
Fixed an issue where, when the customer upgraded from 5.2.12-26 to 6.1.1-6 on several devices, several devices received blue screen error messages. To fix the problem, the customer completely uninstalled the 5.x version of GlobalProtect before upgrading to 6.1.1.
|
||||
|
||||
## GPC-18207
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Android devices and the block list was configured through mobile device management (MDM), the block list did not work as expected and the traffic was not blocked as per the configuration.
|
||||
|
||||
## GPC-17875
|
||||
|
||||
Fixed an issue where,when the GlobalProtect app was installed on iOS devices, the app got stuck in the Connecting state and users had to restart the device to connect to the app.
|
||||
|
||||
## GPC-17635
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on iOS devices, users were unable to send logs ( Help > Send Logs) through apps other than iOS Mail Client. Users can now share the logs using any file sharing app (e.g. Gmail) so that administrators can analyze the logs.
|
||||
|
||||
## GPC-17435
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on iOS devices and configured with On-Demand mode, the app displayed the following erroneous pop-up message:
|
||||
|
||||
GlobalProtect Always-On mode is enabled. Please sign in to continue.
|
||||
|
||||
## GPC-16741
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on iOS devices, users could not connect the iOS device to a manual gateway even though the GlobalProtect portal was configured with two external manual gateways.
|
||||
|
||||
## GPC-15137
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Android devices, the users could not connect to the app due to the following error:
|
||||
|
||||
ANDROID_ACTION_START_VNIC, ret=failed.
|
||||
@@ -0,0 +1,29 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect-iOS
|
||||
version: 6.1.10
|
||||
---
|
||||
|
||||
## 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-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-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.
|
||||
@@ -0,0 +1,61 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect-iOS
|
||||
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.
|
||||
@@ -0,0 +1,107 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect-iOS
|
||||
version: 6.1.4
|
||||
---
|
||||
|
||||
## GPC-19340
|
||||
|
||||
Fixed an issue where the GlobalProtect app failed to send HIP reports hourly.
|
||||
|
||||
## GPC-19331
|
||||
|
||||
Fixed an issue where, when SAML authentication was used to authenticate to the GlobalProtect app, the app used an unknown username SAMLUser which was not configured instead of the actual username of the user, which caused an authentication failure.
|
||||
|
||||
## GPC-19289
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Linux devices with Ubuntu 22.04, the app was unable to collect HIP reports.
|
||||
|
||||
## GPC-19280
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app transitions from pre-logon to user-logon tunnel, the app did not display the list of gateways for the users to change the gateway. The gateway list was displayed only when the app was refreshed.
|
||||
|
||||
## GPC-19193
|
||||
|
||||
Fixed an issue where the GlobalProtect app was unable to fetch Windows firewall and antimalware information correctly.
|
||||
|
||||
## GPC-19187
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app version 6.0.8 or 6.0.7 was installed on endpoints running macOS Sonoma 14.1, the PanGPS did not work as expected.
|
||||
|
||||
## GPC-19162
|
||||
|
||||
Fixed an issue where, when the user upgraded the GlobalProtect version to 5.2.13 or later version, the HIP report displayed the DLP Digital Guardian Agent as disabled.
|
||||
|
||||
## GPC-19153
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on iOS devices, the users had to reconnect to the GlobalProtect app several times in a day. Users were prompted to enter the credentials every time they tried to reconnect.
|
||||
|
||||
## GPC-19143
|
||||
|
||||
Fixed an issue where the users were unable to choose the correct certificate for the app as the configured registry value previousCertificate did not work as expected.
|
||||
|
||||
## GPC-19104
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP report failed to detect the Real Time Protection status for Cortex XDR, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-19083
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the Connection tab under app Settings did not display the connection status and the refresh connection did not work when the Settings window was opened.
|
||||
|
||||
## GPC-19061
|
||||
|
||||
Fixed an issue where GlobalProtect detected an incorrect Real-Time Protection status for Crowdstrike Falcon during HIP checks for antimalware.
|
||||
|
||||
## GPC-19060
|
||||
|
||||
Fixed an issue where when the GlobalProtect app was installed on devices running macOS, the Connection tab under app Settings did not display the connection status when the app was changed from a non-tunneled gateway to a tunneled gateway.
|
||||
|
||||
## GPC-19044
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Windows devices and the user changed the network from wired to wireless within the organization, the device displayed a blue screen.
|
||||
|
||||
## GPC-19023
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app version 5.2.13 was installed on devices running macOS, the users were unable to connect to the Zoom application.
|
||||
|
||||
## GPC-19009
|
||||
|
||||
Fixed an issue where, when SAML authentication was used to authenticate to the GlobalProtect app and the user changed the gateway to a manual gateway, the app stayed in the Connecting stage.
|
||||
|
||||
## GPC-18983
|
||||
|
||||
Fixed an issue where the Central Authentication Service (CAS) authentication did not work when the GlobalProtect app was connected to an internal gateway and the app repeatedly opened the SAML authentication page.
|
||||
|
||||
## GPC-18968
|
||||
|
||||
Fixed an issue where the GlobalProtect app displayed, You are on the internal corporate network message when users were on a public network. Users had to reboot the system to resolve this issue.
|
||||
|
||||
## GPC-18903
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Linux devices running on Red Hat version 9, the resolv.conf file was not getting updated with GlobalProtect DNS servers as expected.
|
||||
|
||||
Users should install/uninstall GlobalProtect app using p_install.shand gp_uninstall.shto fix resolve this issue.
|
||||
|
||||
## GPC-18703
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check did not detect the Trellix Endpoint Security application, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-18854
|
||||
|
||||
Fixed an issue where users were prompted twice to authenticate using SAML authentication when used with CAS authentication and authentication override cookie, the GlobalProtect app got stuck in the Connecting stage while trying to connect.
|
||||
|
||||
## GPC-18828
|
||||
|
||||
Fixed an issue where split tunnel CNAME records were created before the GlobalProtect tunnel was established.
|
||||
|
||||
## GPC-18525
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Linux devices running on Ubuntu 22.04, the app got disconnected intermittently with the error message: Failed to read notify event buffer, error: Resource temporarily unavailable.
|
||||
|
||||
## GPC-16975
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the screen reader did not announce the name of the GlobalProtect gateway when the gateway was marked with the star symbol.
|
||||
|
||||
## GPC-16597
|
||||
|
||||
Fixed an issue where the GlobalProtect app stopped working when the app was upgraded from version 5.2.8 to 6.0.3.
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect-iOS
|
||||
version: 6.1.5
|
||||
---
|
||||
|
||||
## GPC-19631
|
||||
|
||||
Fixed an issue where when the GlobalProtect app is installed on iOS devices, the GlobalProtect app got disconnected and reconnected intermittently when the user was trying to upload files.
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect-iOS
|
||||
version: 6.1.6
|
||||
---
|
||||
|
||||
## GPC-21463
|
||||
|
||||
Fixed an issue where the HIP report did not contain the service set identifier (SSID (service set identifier) and internet service provider (ISP) information when the GlobalProtect app was installed on iOS devices.
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect-iOS
|
||||
version: 6.1.7
|
||||
---
|
||||
|
||||
## GPC-19861
|
||||
|
||||
A fix was made to address insufficient certification validation vulnerability in GlobalProtect app software for iOS platform (CVE-2024-5921).
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect-iOS
|
||||
version: 6.1.9
|
||||
---
|
||||
|
||||
## GPC-23347
|
||||
|
||||
Fixed an issue where saved GlobalProtect app's username/password was cleared, requiring users to enter credentials again.
|
||||
Reference in New Issue
Block a user