206 lines
9.5 KiB
Markdown
206 lines
9.5 KiB
Markdown
---
|
||
type: Addressed
|
||
product: GlobalProtect-Linux
|
||
version: 6.1.3
|
||
---
|
||
|
||
## GPC-19336
|
||
|
||
Fixed an issue where the ADEM portal did not display user information such as User-ID when the ADEM portal was changed from on-premises to Prisma Access.
|
||
|
||
## GPC-18964
|
||
|
||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS and the user upgraded the GlobalProtect version from 6.0.5 to 6.2.1, the app got disconnected after 10 minutes.
|
||
|
||
## GPC-18913
|
||
|
||
Fixed an issue where the GlobalProtect app changed the connection status to Not Connected even though the app was connected to the internal gateway.
|
||
|
||
## GPC-18907
|
||
|
||
Fixed an issue where the GlobalProtect app on macOS endpoints did not query the secondary DNS (when primary DNS is not responding) when the domain was part of the exclude domain list (both network and DNS).
|
||
|
||
## 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-18599
|
||
|
||
Fixed an issue where Linux endpoints could not resolve FQDNs when the GlobalProtect tunnel was connected because the host stopped listening to UDP/53 on the loopback IP address.
|
||
|
||
## 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-18566
|
||
|
||
Fixed an issue where the GlobalProtect app incorrectly displayed the gateway as internal when it was connected to an external gateway.
|
||
|
||
## GPC-18528
|
||
|
||
Fixed an issue where the GlobalProtect HIP check incorrectly detected the version for KES 12 (Kaspersky Endpoint Security), which caused the device to fail the HIP check.
|
||
|
||
## GPC-18512
|
||
|
||
Fixed an issue where, when the GlobalProtect app was installed on Linux devices running Ubuntu 22.04 or REHL 9.1, the app got disconnected periodically.
|
||
|
||
## GPC-18471
|
||
|
||
Fixed an issue where, when multiple wa_3rd_party_host_64.exe processes persisted even after the HIP check was performed, 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-18383
|
||
|
||
Fixed an issue where the GlobalProtect app failed to connect on Windows 11 endpoints with error Could not connect to the GlobalProtect service.
|
||
|
||
## 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-18367
|
||
|
||
Fixed an issue where, when pre-logon was configured for the GlobalProtect app, the GlobalProtect portal displayed the FQDN or IP address of the gateway and not the gateway name. With this fix, the portal displays the gateway name instead of FQDN or IP address.
|
||
|
||
## 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 message : Connected - Inter.... instead of Connected.
|
||
|
||
## 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-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 devices.
|
||
|
||
## 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-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-18155
|
||
|
||
Fixed an issue where, when the GlobalProtect app was installed on Linux devices, the app displayed the text in an incorrect format and the users were unable to read the information displayed on the app.
|
||
|
||
## GPC-18146
|
||
|
||
Fixed an issue where, when the GlobalProtect app was installed on Windows devices, the GlobalProtect HIP check did not detect the correct details for Cortex XDR, which caused the device to fail the HIP check.
|
||
|
||
## 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-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-17914
|
||
|
||
Fixed an issue where, when the GlobalProtect app was installed on macOS endpoints and split tunnel was configured based on the application, the Zoom app got disconnected intermittently.
|
||
|
||
## 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-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-17492
|
||
|
||
Fixed an issue where, when the traffic enforcer setting was applied for pre-logon and the GlobalProtect app was disconnected, the new user setting did not get updated and the pre-logon setting was still applicable.
|
||
|
||
## 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-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-16609
|
||
|
||
Fixed an issue where, when the GlobalProtect app was installed on Windows devices and the screen displayed GlobalProtect app connection status incorrectly when the device was locked.
|
||
|
||
## 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.
|
||
|
||
## GPC-16441
|
||
|
||
Fixed an issue where the GlobalProtect app connection failed when both GlobalProtect Enforcer and Endpoint Traffic Policy Enforcement were enabled.
|
||
|
||
## 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.
|