Remove dates from issue filenames
This commit is contained in:
@@ -0,0 +1,107 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect
|
||||
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.
|
||||
Reference in New Issue
Block a user