226 lines
11 KiB
Markdown
226 lines
11 KiB
Markdown
---
|
||
type: Addressed
|
||
product: GlobalProtect
|
||
version: 6.0.8
|
||
---
|
||
|
||
## GPC-18822
|
||
|
||
Fixed an issue where, when the GlobalProtect app was installed on Windows devices and the device was reset using the Microsoft Recovery tool, the GlobalProtect app was not properly displayed.
|
||
|
||
## GPC-18788
|
||
|
||
Fixed an issue where the GlobalProtect HIP check did not detect McAfee Total Protection as an anti-malware application, which caused the device to fail the HIP check.
|
||
|
||
## GPC-18733
|
||
|
||
Fixed an issue where the hyperlinks with the URLs containing the = character in the HIP notification message did not work as expected and the page did not open when the user clicked the URL.
|
||
|
||
## GPC-18728
|
||
|
||
Fixed an issue where the **I Agree** option on the GlobalProtect app Welcome page did not work as expected when the user selected the option using a keyboard.
|
||
|
||
## GPC-18720
|
||
|
||
Fixed an issue where the GlobalProtect app became unresponsive when the user clicked the **ESC** button during authentication using a hard token.
|
||
|
||
## GPC-18598
|
||
|
||
Fixed an issue where the GlobalProtect SSO tile was selected instead of the Windows Password tile in the Windows Login screen even though the registry key **MakeGPCPDefault** was set to **No**.
|
||
|
||
## GPC-18594
|
||
|
||
Fixed an issue where the GlobalProtect app was unable to send HIP reports when the app was connected using IPv6 address.
|
||
|
||
## GPC-18568
|
||
|
||
Fixed an issue where the Captive Portal Detection functionality of the GlobalProtect app did not work as expected when the users used public Wi-Fi hotspots and the GlobalProtect app failed to retrieve cached configuration without a username.
|
||
|
||
## GPC-18543
|
||
|
||
Fixed an issue where the GlobalProtect app was installed on Windows devices with the split tunnel feature and when the user excluded the access route, the GlobalProtect app excluded only the route and did not exclude the subnets.
|
||
|
||
## GPC-18471
|
||
|
||
Fixed an issue where, when multiple wa_3rd_party_host_64.exe processes persisted even after the HIP check was performed due to which the GlobalProtect app stopped working.
|
||
|
||
## GPC-18426
|
||
|
||
Fixed an issue where, when the GlobalProtect app was configured with the **Disable GlobalProtect**option set to **Allow with Ticket**, the app did not display the correct **Disable Duration** time.
|
||
|
||
## GPC-18379
|
||
|
||
Fixed an issue where, when the IP address type was set to IPv4 and IPv6, the GlobalProtect app could connect only to the manual gateway instead of connecting to the best available gateway.
|
||
|
||
## GPC-18336
|
||
|
||
Fixed an issue where, when the GlobalProtect app got automatically connected after a system reboot even though the connection method configured was On-Demand.
|
||
|
||
## GPC-18318
|
||
|
||
Fixed an issue where, when the GlobalProtect app was connected to the internal gateway, the app displayed the incorrect message : **Connected - Inter....** instead of **Connected**.
|
||
|
||
## GPC-18285
|
||
|
||
Fixed an issue where the GlobalProtect app displayed an incorrect gateway location name instead of the correct gateway location configured by the user.
|
||
|
||
## GPC-18281
|
||
|
||
Fixed an issue where the MSI install logs showed mutiple messages for Autonomous DEM installation.
|
||
|
||
## GPC-18263
|
||
|
||
Fixed an issue where, when the GlobalProtect app was configured with Endpoint Traffic Policy Enforcement and Disable Local Subnet Access (DLSA), the Autonomous DEM reported users’ internet connection as down.
|
||
|
||
## GPC-18251
|
||
|
||
Fixed an issue where the GlobalProtect HIP check did not detect McAfee LiveSafe as an anti-malware application, which caused the device to fail the HIP check.
|
||
|
||
## GPC-18242
|
||
|
||
Fixed an issue where the end users were prompted to enter Windows login credentials (username and password) instead of their PIV Badge PIN when the system was unlocked or after a system reboot.
|
||
|
||
## GPC-18230
|
||
|
||
Fixed an issue where, when the user entered credentials during SAML authentication after the set internal login timer, the app displayed an authentication failed message without providing the reason. The **Retry** button on the app web interface did not work properly when using an embedded browser for authentication. The **Retry** button was not fully visible on the embedded browser.
|
||
|
||
## GPC-18223
|
||
|
||
Fixed an issue where GlobalProtect experienced a prolonged connection time when IPv6 was disabled on Windows, but GlobalProtect Portal was configured to assign IPv6 addresses.
|
||
|
||
## GPC-18200
|
||
|
||
Fixed an issue where the GlobalProtect HIP check did not detect McAfee LiveSafe as an antivirus application, which caused the device to fail the HIP check.
|
||
|
||
## GPC-18175
|
||
|
||
Fixed an issue where users were prompted to enter their credentials even when the GlobalProtect app was configured for authenticating with either Authentication Profile /Cookie or Client Certificate.
|
||
|
||
## GPC-18173
|
||
|
||
Fixed an issue where the vertical scroll bar on the GlobalProtect app web interface did not work properly when users tried to select the certificate from the drop-down.
|
||
|
||
## GPC-18171
|
||
|
||
Fixed an issue where users were unable to select the external gateway manually when connected to the internal network. The GlobalProtect stayed in Connecting state and users had to manually disconnect the connection and connect to the internal network to exit the Connecting state.
|
||
|
||
## GPC-18167
|
||
|
||
Fixed an issue where the GlobalProtect app displayed the Prisma Access gateways that were not set for manual selection.
|
||
|
||
## GPC-18157
|
||
|
||
Fixed an issue where the GlobalProtect app displayed the Credential Provider language in English when the system language was German.
|
||
|
||
## GPC-18135
|
||
|
||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the GlobalProtect HIP check detected the WithSecure antivirus software as XProtect, which caused the device to fail the HIP check.
|
||
|
||
## GPC-18107
|
||
|
||
Fixed an issue where the GlobalProtect HIP check did not detect McAfee LiveSafe – Internet Security, which caused the device to fail the HIP check.
|
||
|
||
## GPC-18092
|
||
|
||
Fixed an issue where GlobalProtect connected to an internal gateway got automatically disconnected after a certain period of time.
|
||
|
||
## GPC-18073
|
||
|
||
Fixed an issue where the GlobalProtect app selected an unexpected gateway due to a latency discrepancy seen between PanGPS and packet capture.
|
||
|
||
## GPC-18060
|
||
|
||
Fixed an issue where the GlobalProtect HIP check did not detect McAfee Total Protection, which caused the device to fail the HIP check.
|
||
|
||
## GPC-18039
|
||
|
||
Fixed an issue where the GlobalProtect HIP check did not detect the Definition Date correctly for the CrowdStrike application, which caused the device to fail the HIP check.
|
||
|
||
## GPC-18036
|
||
|
||
Fixed an issue where, when the No direct access to local network option was enabled on the GlobalProtect app with access routes excluded from the GlobalProtect VPN tunnel, the feature did not work as expected when Endpoint Traffic Policy Enforcement was enabled.
|
||
|
||
## GPC-17896
|
||
|
||
Fixed an issue where users were unable to connect to GlobalProtect gateway when only one external gateway was added due to the following error: **Cannot Verify Server Certificate of Gateway**.
|
||
|
||
## GPC-17877
|
||
|
||
Fixed an issue where the GlobalProtect HIP check incorrectly detected Sophos Endpoint Agent version 3.86.1, which caused the device to fail the HIP check.
|
||
|
||
## GPC-17795
|
||
|
||
Fixed an issue where the GlobalProtect HIP check did not detect the Xcitium Enterprise, the Endpoint Protection Platform by COMODO, which caused the device to fail the HIP check.
|
||
|
||
## GPC-17776
|
||
|
||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS and GlobalProtect enforcer was configured with allowed FQDNs, users were still able to access the internet and other public domains.
|
||
|
||
## GPC-17762
|
||
|
||
Fixed an issue when the GlobalProtect app was configured with the option **Allow User to Disable GlobalProtect App** with comment, the option did not work as expected.
|
||
|
||
## GPC-17748
|
||
|
||
Fixed an issue where the GlobalProtect HIP check did not detect the Real-Time Protection status correctly for the CrowdStrike Falcon application, which caused the device to fail the HIP check.
|
||
|
||
## GPC-17740
|
||
|
||
Fixed an issue where, when the GlobalProtect app was connected through the Prisma Access gateway, the upload speed of the internet was reduced to 2 Mbps.
|
||
|
||
## GPC-17657
|
||
|
||
Fixed an issue, where the GlobalProtect app got stuck in Selecting Best Gateway status when the device woke up from sleep mode. Users had to reboot the device to connect to the app.
|
||
|
||
## GPC-17640
|
||
|
||
Fixed an issue where, when the upgrade script update_tmp.bat was used, the error message did not display the correct exit timeout for the PanGPS uninstall process.
|
||
|
||
## GPC-17518
|
||
|
||
Fixed an issue where the GlobalProtect app displayed the status as 'Connected-Internal even when the app was not connected.
|
||
|
||
## GPC-17436
|
||
|
||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the upload speed of the internet was reduced after a version upgrade.
|
||
|
||
## GPC-17206
|
||
|
||
Fixed an issue where, when Internal Host Detection (IHD) was enabled but failed to detect the internal network properly, the app failed to switch to the external gateway when users switched from an internal network to an external network.
|
||
|
||
## GPC-17204
|
||
|
||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the certificate information was not accessible even though the GlobalProtect app had full access to the certificate store.
|
||
|
||
## GPC-17161
|
||
|
||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the GlobalProtect app failed to reconnect and continued to stay in the Connecting state after the device woke up from Modern Standby mode.
|
||
|
||
## GPC-17115
|
||
|
||
Fixed an issue where the GlobalProtect HIP check did not detect the Cortex Anti-Malware status properly after a system reboot, which caused the device to fail the HIP check.
|
||
|
||
## GPC-17086
|
||
|
||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, users were unable to make a connection to an internal gateway using the default browser for SAML authentication.
|
||
|
||
## GPC-17001
|
||
|
||
Fixed an issue where, when the GlobalProtect app was installed on devices running on macOS, the app did not display the **Connect** button and **Refresh Connection** button properly.
|
||
|
||
## GPC-16584
|
||
|
||
Fixed an issue where the GlobalProtect HIP check did not detect the CrowdStrike antivirus software correctly, causing the device to fail the HIP check.
|
||
|
||
## GPC-16397
|
||
|
||
Fixed an issue where the GlobalProtect app was installed on devices running macOS, a blank GlobalProtect app user interface was displayed instead of the correct page.
|
||
|
||
## GPC-15697
|
||
|
||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, users were able to select **All Gateways** heading on the page which was not an option for the users to select. This issue happened on the app interface with a non-English language.
|
||
|
||
## GPC-15262
|
||
|
||
Fixed an issue where, when single sign-on (SSO) for Smart Card was used for authentication, users were prompted to enter a PIN instead of password on the Windows login screen.
|