106 lines
4.9 KiB
Markdown
106 lines
4.9 KiB
Markdown
---
|
|
type: Addressed
|
|
product: GlobalProtect
|
|
version: 6.2.8-h4
|
|
---
|
|
|
|
## GPC-23839
|
|
|
|
Fixed an issue that caused the GlobalProtect 6.3.3 HIP report to fail with the error Method: **WAAPI_MID_GET_AGENT_STATE**.
|
|
|
|
## GPC-23786
|
|
|
|
Fixed an issue where the agent-msg log (**Panorama** > **Monitor** > **GlobalProtect**) was not generated when a user disabled the GlobalProtect app and logged out of the gateway.
|
|
|
|
## GPC-23760
|
|
|
|
GlobalProtect app version 6.3.3 using SAML with the embedded browser loses cursor focus in the password field, requiring users to click in the password field before entering their password.
|
|
|
|
## GPC-23752
|
|
|
|
Fixed an issue where the GlobalProtect app failed to authenticate to the portal and gateway after a machine certificate was renewed by Intune MDM. A reboot was required to restore the connection.
|
|
|
|
## GPC-23746
|
|
|
|
Fixed an issue where the GlobalProtect HIP check incorrectly detected status for Symantec Endpoint Protection, which caused the device to fail the HIP check.
|
|
|
|
## GPC-23646
|
|
|
|
Fixed an issue where the GlobalProtect app ignores the new gateway-generated authentication override cookie and continues to use the old, expired portal cookie when using the cached portal configuration. As a result, the authentication override cookie generated by a successful SAML authentication to a gateway is replaced by the old, expired portal cookie during successive authentications, causing the gateway to prompt for SAML authentication repeatedly.
|
|
|
|
## GPC-23616
|
|
|
|
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the following error **TransparentProxy: openWithLocalEndpoint failed** occurred in PanNExt.log when using an IPv6 address.
|
|
|
|
## GPC-23583
|
|
|
|
Fixed an issue where the pre-login tunnel rename timeout notification would overlay other system tray icons, preventing users from accessing them
|
|
|
|
## GPC-23558
|
|
|
|
Fixed an issue where GlobalProtect clients using SAML with Ping Federate did not save the SAML token upon reboot or restart of the pangps service, requiring users to re-authenticate even when the token was not expired. This issue affected GlobalProtect app version 6.3.3 when SAML authentication was configured in Prisma Access and not in Cloud Identity Engine.
|
|
|
|
## GPC-23519
|
|
|
|
Fixed an issue where GlobalProtect HIP reports on MacBooks intermittently failed with an **Invalid client IP** error, preventing users from accessing resources over the GlobalProtect tunnel. This issue occurred after a system network change when GlobalProtect attempted to send the HIP report to an external gateway while the tunnel was disconnected. This issue affected MacBooks running GlobalProtect version 6.2.5.
|
|
|
|
## GPC-23514
|
|
|
|
Fixed an issue where, when using a screen reader on Windows or macOS, the GlobalProtect app's **Settings** button did not announce the available options for the end users.
|
|
|
|
## GPC-23488
|
|
|
|
Fixed an issue where the HIP report intermittently detected MacOS XProtect Real Time Protection status as disabled.
|
|
|
|
## GPC-23468
|
|
|
|
Fixed an issue where the GlobalProtect HIP check failed to detect the correct version of Forticlient Antivirus, which caused the device to fail the HIP check.
|
|
|
|
## GPC-23441
|
|
|
|
Fixed an issue where the GlobalProtect installation failed after a transparent upgrade automatically uninstalled the previous version.
|
|
|
|
## GPC-23428
|
|
|
|
Fixed an issue where the username and password fields in the GlobalProtect app had incorrect labels.
|
|
|
|
## GPC-23417
|
|
|
|
Fixed an issue where SAML authentication with Azure AD, using Cisco Duo EAM, failed after upgrading to GlobalProtect version 6.2.8
|
|
|
|
## GPC-23404
|
|
|
|
Fixed an issue where the Host Information Profile (HIP) check was unable to accurately identify key details from third-party security products.
|
|
|
|
## GPC-23403
|
|
|
|
Fixed an issue where the GlobalProtect HIP report failed to detect the status of SentinelOne, causing the device to fail the HIP check
|
|
|
|
## GPC-23361
|
|
|
|
Fixed an issue where the GlobalProtect HIP report did not detect the Status for Zoho corporation - ManageEngine Patch Manager Plus Agent, which caused the device to fail the HIP check.
|
|
|
|
## GPC-23283
|
|
|
|
Fixed an issue where GlobalProtect was unable to set [exclude/include] 0.0.0.0/netmask routes on Mac endpoint.
|
|
|
|
## GPC-23142
|
|
|
|
Fixed an issue where an Explicit Proxy token refresh would fail with the message EP TOKEN configuration is NULL, causing the GlobalProtect app to get stuck in a Connecting state.
|
|
|
|
## GPC-23095
|
|
|
|
Fixed and issue where the GlobalProtect HIP report failed to detect the Symantec DLP software, which caused the device to fail the HIP check.
|
|
|
|
## GPC-22353
|
|
|
|
Fixed an issue where a comment was not visible in the GlobalProtect logs when GlobalProtect was disabled with-comment.
|
|
|
|
## GPC-21745
|
|
|
|
Fixed an issue where the GlobalProtect HIP check failed to detect Workspace ONE status, which caused the device to fail the HIP check.
|
|
|
|
## GPC-20617
|
|
|
|
Fixed an issue where a notification appeared on the GlobalProtect app every 10 seconds asking the end-user to re-authenticate. This notification appeared during the pre-logon tunnel rename timeout period.
|