206 lines
9.5 KiB
Markdown
206 lines
9.5 KiB
Markdown
---
|
|
type: Addressed
|
|
product: GlobalProtect
|
|
version: 6.0.7
|
|
---
|
|
|
|
## GPC-18071
|
|
|
|
Fixed an issue where, when the GlobalProtect app was installed on Android devices with Android 13, the app stopped working while sending GPS notifications.
|
|
|
|
## GPC-17921
|
|
|
|
Fixed an issue where, when the language was set to Japanese, the time to connect was not displayed properly when **Disconnect Timeout** for the app was configured.
|
|
|
|
## GPC-17831
|
|
|
|
Fixed an issue where the GlobalProtect app reported the computer name differently from the computer name displayed in Autonomous DEM causing a data discrepancy.
|
|
|
|
## GPC-17771
|
|
|
|
Fixed an issue where the GlobalProtect app stopped working abruptly.
|
|
|
|
## GPC-17754
|
|
|
|
Fixed an issue where the GlobalProtect app did not detect Smart Card removal every time the user removed the card and due to which the app was not getting disconnected on **On-Demand** tunnel mode.
|
|
|
|
## GPC-17575
|
|
|
|
Fixed an issue where the GlobalProtect HIP check incorrectly detected Windows firewall as disabled, which caused the device to fail the HIP check.
|
|
|
|
## GPC-17556
|
|
|
|
Fixed an issue where the GlobalProtect app would get stuck at Connecting state when the user tried to close the browser window for SAML authentication after configuring **On-Demand** mode for the app.
|
|
|
|
## GPC-17473
|
|
|
|
Fixed an issue where the GlobalProtect portal and gateway selection list were displayed in the table format and not as menu item.
|
|
|
|
## GPC-17460
|
|
|
|
Fixed an issue where, when the GlobalProtect app was installed on Windows 10 or Windows11 devices, and when the user tried to authenticate using SAML authentication, the app did not display the **Term of Use** pop-up on the Welcome page properly.
|
|
|
|
## GPC-17451
|
|
|
|
Fixed an issue where the ADEM agent remained in the disabled state after connecting to a Prisma Access portal configured to enable ADEM on the GlobalProtect endpoints after switching from an on-premises portal that had ADEM disabled in the app configuration that was pushed to the endpoint.
|
|
|
|
## GPC-17406
|
|
|
|
Fixed an issue where GlobalProtect HIP check did not detect the new version of Trellix Drive Encryption correctly which caused the device to fail the HIP check.
|
|
|
|
## BGPC-17401
|
|
|
|
Fixed an issue where the GlobalProtect app was installed on the Chromebook, the app got disconnected when the ChromeOS detected policy changes related to location information.
|
|
|
|
## GPC-17393
|
|
|
|
Fixed an issue where, when the GlobalProtect app was installed on Windows 10 devices and the language was set to Japanese, IpConfig.txt and Systeminfo.txt in the GlobalProtectLogs.zip did not work properly.
|
|
|
|
## GPC-17337
|
|
|
|
Fixed an issue where the GlobalProtect app got disconnected due to a HIP reporting error that prevented the app from sending HIP reports to the gateway.
|
|
|
|
## GPC-17335
|
|
|
|
Fixed an issue where the user interface of the GlobalProtect app was going over-sized when the system woke up from the sleep mode.
|
|
|
|
## GPC-17299
|
|
|
|
Fixed an issue where the GlobalProtect app did not display LDAP password expiration notification on consecutive connection attempts when the user tried to authenticate using the LDAP authentication method.
|
|
|
|
## GPC-17252
|
|
|
|
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the app did not try to auto-connect to the gateway after exceeding the **Disable Timeout** value.
|
|
|
|
## GPC-17227
|
|
|
|
Fixed an issue where the tunnel was still up and connected even when the user disconnected the GlobalProtect app.
|
|
|
|
## GPC-17205
|
|
|
|
Fixed an issue where GlobalProtect failed to decrypt HipPolicy.dat on endpoints, which caused the device to fail the HIP check for anti-malware.
|
|
|
|
## GPC-17137
|
|
|
|
Fixed an issue where, when user clicked the Network sign-in icon on the Windows login page, an icon with the name image was displayed instead of the portal IP address/ URL.
|
|
|
|
## GPC-17128
|
|
|
|
Fixed an issue where the Client Certificate had a blank Subject with SAN as the critical extension, which caused the endpoints to fail the HIP check.
|
|
|
|
## GPC-17099
|
|
|
|
Fixed an issue where devices with Driver Verified enabled and configured to monitor the PAN virtual adapter driver (pangpd.sys) displayed the DRIVER_VERIFIER_DETECTED_VIOLATION Blue Screen error
|
|
|
|
## GPC-17041
|
|
|
|
Fixed an issue where, when the GlobalProtect app was installed on Windows 10 devices and the language was set to Japanese, IpConfig.txt in the GlobalProtectLogs.zip did not work properly.
|
|
|
|
## GPC-17011
|
|
|
|
Fixed an issue where the GlobalProtect app tried to send HIP reports even when the device was on Modern Standby mode.
|
|
|
|
## GPC-17000
|
|
|
|
Fixed an issue where the GlobalProtect app would get stuck at Connecting state when user tried to authenticate with SAML authentication method using the embedded browser and user clicked **Cancel** on the certificate prompts.
|
|
|
|
## GPC-16978
|
|
|
|
Fixed an issue where the GlobalProtect app took a long time to establish a connection due to an erroneous packet capture process.
|
|
|
|
## GPC-16959
|
|
|
|
Fixed an issue where the Endpoint Traffic Policy Enforcement feature was causing the GlobalProtect app to drop Slack WebSocket outbound traffic on macOS endpoints.
|
|
|
|
## GPC-16788
|
|
|
|
Fixed an issue where when the GlobalProtect app was installed on devices running macOS, HIP check did not detect the Tanium Client correctly which caused the device to fail the HIP check.
|
|
|
|
## GPC-16682
|
|
|
|
Fixed an issue where the GlobalProtect app did not honor the **Disable Timeout** value and would automatically reconnect after the user restarted two times due to an issue with the new splash screen.
|
|
|
|
## GPC-16645
|
|
|
|
Fixed an issue where the GlobalProtect app couldn't display the Verify text box when using the full 255 characters for Radius DUO Authentication on Windows devices.
|
|
|
|
## GPC-16631
|
|
|
|
Fixed an issue where GlobalProtect logs forwarded from CDL to syslog-ng and Splunk were arriving in multiline and single line mode randomly.
|
|
|
|
## GPC-16627
|
|
|
|
Fixed an issue where the GlobalProtect HIP check incorrectly detected the Anti-Malware information for the McAfee Total Protection Antivirus software application, which caused the device to fail the HIP check.
|
|
|
|
## GPC-16609
|
|
|
|
Fixed an issue that the correct status is not displayed GlobalProtect status in the Windows lock screen when the gateway is connected.
|
|
|
|
## GPC-16575
|
|
|
|
Fixed an issue where GlobalProtect users were intermittently unable to log in to the gateway when using the user logon connect method because **Enforce GlobalProtect Connection for Network Access**was enabled immediately after portal login, blocking access to the gateway login URL.
|
|
|
|
## GPC-16572
|
|
|
|
Fixed an issue where the GlobalProtect HIP check took longer than expected to collect the HIP information causing the device to fail the HIP check.
|
|
|
|
## GPC-16441
|
|
|
|
Fixed an issue where the GlobalProtect app connection failed when the user enabled both Globalprotect Enforcer and Endpoint Traffic Policy Enforcement.
|
|
|
|
## 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-16297
|
|
|
|
Fixed an issue where users were unable to see the available list of eligible gateways to select the gateway manually when the best available gateway failed.
|
|
|
|
## GPC-16267
|
|
|
|
Fixed an issue where the portal status did not show as Connected even when the portal was accessible after a reboot and the portal status was Using cached portal config, which did not trigger the transparent upgrade.
|
|
|
|
## GPC-16126
|
|
|
|
Fixed an issue where the GlobalProtect app did not display the certificate name in the Client Certificate selection field properly.
|
|
|
|
## GPC-16003
|
|
|
|
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the app was not connected when the proxy was configured for Safari or Chrome.
|
|
|
|
## GPC-16002
|
|
|
|
Fixed an issue where the GlobalProtect HIP check detected the device as Windows firewall enabled even though the firewall was disabled on the device.
|
|
|
|
## GPC-15968
|
|
|
|
Fixed an issue where the GlobalProtect app was stuck in Connecting state when users failed to authenticate with SAML and using an embedded browser. Users were unable to disconnect the app and had to reboot the device.
|
|
|
|
## GPC-15251
|
|
|
|
Fixed an issue where, when the GlobalProtect app was installed on Android devices and connected with **Always-On**(User logon) option, the app displayed the following notification twice.
|
|
|
|
**Always on VPN is currently enabled. Disabling the VPN connection could result in loss of network access.**
|
|
|
|
## GPC-15234
|
|
|
|
Fixed an issue where the app would get stuck at Connecting'state while trying to connect to a gateway.
|
|
|
|
## GPC-15231
|
|
|
|
Fixed an issue where, when the GlobalProtect app was installed on Android devices and connected with **Always-On** option, the app displayed the following notification twice and the users were unable to clear the notifications.
|
|
|
|
**Always on VPN is currently enabled. Disabling the VPN connection could result in loss of network access.**
|
|
|
|
## GPC-15111
|
|
|
|
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the screen reader repeatedly announced tabs, **Add** button and portals table on the user interface. The screen reader should announce the user interface elements only once.
|
|
|
|
## GPC-15080
|
|
|
|
Fixed an issue where the split tunnel was configured based on the destination domain, split tunneling did not work as expected when IPv6 traffic exclusion was configured.
|
|
|
|
## GPC-14672
|
|
|
|
Fixed an issue where, when the GlobalProtect app was installed on macOS devices and **No direct access to local network** option was enabled with access routes excluded from the GlobalProtect VPN tunnel, the excluded traffic was not sent through the physical adapter on the endpoint. Following this, the users were unable to access the local physical network devices such as printers.
|