Initial prototype
This commit is contained in:
@@ -0,0 +1,177 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect
|
||||
version: 6.3.1
|
||||
---
|
||||
|
||||
## GPC-21022
|
||||
|
||||
Fixed an issue where the GlobalProtect re-authentication prompt appeared in the background instead of the foreground after deploying Okta FastPass.
|
||||
|
||||
## GPC-20895
|
||||
|
||||
Fixed an issue where a macOS GlobalProtect app user was able to modify or add a new portal even though the portal agent configuration specified Allow User to Change Portal Address = NO and Allow user to Sign Out from GlobalProtect App = No .
|
||||
|
||||
## GPC-20864
|
||||
|
||||
Fixed an issue where the GlobalProtect embedded browser login window did not stay pinned to the front of all open windows on Windows and MAC computers.
|
||||
|
||||
## GPC-20839
|
||||
|
||||
Fixed an issue where a macOS user was unable to connect to the GlobalProtect app.
|
||||
|
||||
## GPC-20722
|
||||
|
||||
Fixed an issue in the GlobalProtect macOS client where the UI incorrectly displayed a "Not Connected" status and a "Connect" button while the user was in the process of connecting to a new gateway.
|
||||
|
||||
## GPC-20645
|
||||
|
||||
Fixed an issue where the GlobalProtect macOS app was stuck in connecting stage when the macOS computer woke from sleep and the user had to restart the computer.
|
||||
|
||||
## GPC-20601
|
||||
|
||||
Fixed an issue where users unable to connect to GlobalProtect after upgrading from version 6.2.2 to 6.2.3 via JAMF.
|
||||
|
||||
## GPC-20595
|
||||
|
||||
Fixed an issue where GlobalProtect users were unable to connect after upgrading to 6.2.3-270 and received a Y our internet access is blocked error during SAML authentication using the embedded browser.
|
||||
|
||||
## GPC-20527
|
||||
|
||||
Fixed an issue where the Conditional Connect method configured for the GlobalProtect app did not work as expected when the user shifted from external network (home) to an internal network (office). Users had to reboot the system to resolve this issue.
|
||||
|
||||
## GPC-20463
|
||||
|
||||
Fixed an issue where the GlobalProtect status panel is not disabled at startup when the Display Status Panel at Startup parameter is set to no.
|
||||
|
||||
## GPC-20442
|
||||
|
||||
Fixed an issue on appliances running PanOS 10.1.11-h1 and GlobalProtect 6.0.10-811 where the tunnel status failed to update to connected immediately after establishment. This problem was specific to IPv4-only clients connecting to dual-stack (IPv4 + IPv6) GlobalProtect gateways or portals.
|
||||
|
||||
## GPC-20427
|
||||
|
||||
Fixed an issue where the GlobalProtect client on Windows 11 devices displayed an error message "The parameter is incorrect" when attempting to connect to a firewall running PAN-OS 10.1.13 with SAML authentication enabled.
|
||||
|
||||
## GPC-20374
|
||||
|
||||
Fixed an issue where users were unable to connect to GlobalProtect if they accidentally clicked decline on the Terms of Service page.
|
||||
|
||||
## GPC-20157
|
||||
|
||||
Fixed an issue where the gateway location was not correctlydisplayed in the Connections panel.
|
||||
|
||||
## GPC-20143
|
||||
|
||||
Fixed an issue where the user was redirected to the Authentication page twice on the default browser for both portal and gateway authentication when SAML was configured.
|
||||
|
||||
## GPC-20114
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the certificate information was incorrect during the portal login phase causing authentication failure.
|
||||
|
||||
## GPC-20112
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check incorrectly detected Real time protection status for Kaspersky Endpoint Security, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-20091
|
||||
|
||||
Fixed an issue where pre-logon failed when the computer was rebooted, when the machine store had an expired and active certificate.
|
||||
|
||||
## GPC-20080
|
||||
|
||||
Fixed an issue where the GlobalProtect logs displayed different event messages for Windows and macOS devices when the Allow User to Disable GlobalProtect App was set to Allow with Passcode for the GlobalProtect app.
|
||||
|
||||
## GPC-20060
|
||||
|
||||
Fixed an issue where it was possible for the GlobalProtect enforcer to be disabled when there was a network change during portal authentication.
|
||||
|
||||
## GPC-20040
|
||||
|
||||
Fixed an issue where GlobalProtect did not re-check for internal gateways when using cached portal configuration and an external network was previously detected.
|
||||
|
||||
## GPC-19991
|
||||
|
||||
Fixed an issue where client certificate authentication between embedded browser and IdP (SAML) fails.
|
||||
|
||||
## GPC-19966
|
||||
|
||||
Fixed an issue where the embedded browser was unable to load the Microsoft IdP login page for the users to authenticate to the GlobalProtect app.
|
||||
|
||||
## GPC-19901
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the app got disconnected and reconnected intermittently.
|
||||
|
||||
## GPC-19889
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Windows machine and Connect Before Logon (CBL) was configured for the app, the app did not start properly when the user logged on to the device.
|
||||
|
||||
## GPC-19840
|
||||
|
||||
Fixed an issue where Mac computers did not display all gateways in the Search Gateway tab.
|
||||
|
||||
## GPC-19833
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Windows devices, the Smart card (Yubikey) authentication did not work when the device woke up from sleep mode.
|
||||
|
||||
## GPC-19753
|
||||
|
||||
Fixed an issue where the GlobalProtect icon could not be selected using the keyboard.
|
||||
|
||||
## GPC-19751
|
||||
|
||||
Fixed an issue where the programmatic and visual label for the GlobalProtect form field was not announced.
|
||||
|
||||
## GPC-19686
|
||||
|
||||
Fixed an issue where translation errors were observed in the GlobalProtect app for French localization.
|
||||
|
||||
## GPC-19659
|
||||
|
||||
Fixed an issue where macOS users were connected to the GlobalProtect app before they agreed to their company’s terms of service.
|
||||
|
||||
## GPC-19513
|
||||
|
||||
Fixed an issue where the GlobalProtect app was trying to use the old portal's authorization cookie to login instead of the newly migrated portal. This happened when the user changed from secondary portal to primary portal or vice versa without signing out.
|
||||
|
||||
## GPC-19475
|
||||
|
||||
Fixed an issue where users got connection errors in an embedded browser after the computer woke up from sleep or when the user switched gateways.
|
||||
|
||||
## GPC-19433
|
||||
|
||||
Fixed an issue where a small white blank page randomly popped up on the device screen distracting the users. This issue occurred while the device was connected to GlobalProtect app.
|
||||
|
||||
## GPC-19373
|
||||
|
||||
Fixed an issue where the HIP remediation pop up is displayed even when the user is disconnected.
|
||||
|
||||
## GPC-18991
|
||||
|
||||
Fixed an issue where the proxy auto-configuration (PAC) files were not restored as expected after a system reboot or when the user disconnected the GlobalProtect app.
|
||||
|
||||
## 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-18702
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Windows devices, the “Allow Manually upgrade failed when the user tried to upgrade the GlobalProtect app version from 6.0.5 to 6.0.7.
|
||||
|
||||
## GPC-18647
|
||||
|
||||
Fixed an issue where the user reported an issue using the Report an Issue option on the GlobalProtect app and the issue was not reported as expected.
|
||||
|
||||
## GPC-17820
|
||||
|
||||
Fixed an issue where Firefox was not supported for proxied traffic in Tunnel and Proxy mode or proxy mode.
|
||||
|
||||
## GPC-17727
|
||||
|
||||
Fixed an issue where when the GlobalProtect app was connected in Tunnel and Proxy mode or proxy mode, SSH traffic could not be sent over the proxy.
|
||||
|
||||
## 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-15750
|
||||
|
||||
Fixed an issue where a hyperlink in a HIP notification opened in the GPO-disabled Internet Explorer 11 browser instead of the default browser.
|
||||
@@ -0,0 +1,191 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect
|
||||
version: 6.3.2
|
||||
---
|
||||
|
||||
## GPC-22087
|
||||
|
||||
Fixed an issue where the GlobalProtect app was unable to validate the certificate from OCSP.
|
||||
|
||||
## GPC-22080
|
||||
|
||||
Fixed an issue where the OCSP requests were being rejected by the OCSP responder with a HTTP 400 Bad Request error due to the absence of the Host header in the OCSP request.
|
||||
|
||||
## GPC-21938
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app version 6.3.x was installed on devices running macOS, the HIP check failed to detect ESET Endpoint Security version 8.
|
||||
|
||||
## GPC-21918
|
||||
|
||||
Fixed an issue where, when the patch management category was excluded for HIP checks, HIP checks were still happening for missing patches which consumed CPU resources on users' machine.
|
||||
|
||||
## GPC-21838
|
||||
|
||||
Fixed an issue in which the GlobalProtect app, when installed on Windows devices, caused a duplicate page to open in the system default browser (Chrome) when the user clicked the hyperlink on the Welcome page with fedmandate on the embedded browser.
|
||||
|
||||
## GPC-21836
|
||||
|
||||
Fixed an issue in GlobalProtect 6.3.1 for macOS where the Refresh Connection option was missing during the Connecting state, specifically for users who upgraded from version 6.3.0.
|
||||
|
||||
## GPC-21778
|
||||
|
||||
Fixed an issue where the GlobalProtect IPSec tunnel got disconnected on GlobalProtect app version 6.2.5 when gpupdate /force command was used to update policy.
|
||||
|
||||
## GPC-21774
|
||||
|
||||
Fixed an issue where the GlobalProtect ARM64 installers for 6.2.5 version did not display the Digital Signatures tab.
|
||||
|
||||
## GPC-21771
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check incorrectly detected Malware Definition Date for Trend Micro Deep Security Agent, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-21733
|
||||
|
||||
Fixed an issue where all the added portals got deleted from the portal list except the connected portal when the GlobalProtect app was upgraded from version 6.2.4 to 6.2.5-788. Users had to manually add them again to resolve the issue.
|
||||
|
||||
## GPC-21604
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS and were connected to the internal gateway, the app did not display the Disconnect option under Settings.
|
||||
|
||||
## GPC-21571
|
||||
|
||||
Fixed an issue where the hyperlink in HIP notification opened up in Webview2 instead of the default browser.
|
||||
|
||||
## GPC-21565
|
||||
|
||||
Fixed an issue where the SAML embedded browser did not remember the username after sign-out, even when the user had selected the check box Remember Me on the SAML embedded browser.
|
||||
|
||||
## GPC-21542
|
||||
|
||||
Fixed an issue where GlobalProtect got stuck in connecting and failed the connection after some time.
|
||||
|
||||
## GPC-21443
|
||||
|
||||
Fixed an issue where GlobalProtect crashed when the PanGPS service was stopped.
|
||||
|
||||
## GPC-21414
|
||||
|
||||
Fixed an issue where the SAML authentication page would occasionally fail to appear due to the usage of a previous SAML pre-login cookie.
|
||||
|
||||
## GPC-21399
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the HIP check for the built-in firewall shows N/A incorrectly.
|
||||
|
||||
The value should be either Yes or No.
|
||||
|
||||
## GPC-21370
|
||||
|
||||
Fixed an issue where the HIP check could not detect Trellix Firewall Status, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-21332
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check incorrectly detected Real Time Protection status for Avast and XProtect, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-21320
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check did not detect Kaspersky Endpoint Security antimalware application which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-21301
|
||||
|
||||
Fixed an issue where, when the user upgraded the GlobalProtect app version to 6.2.4 with SAML authentication, users were unable to connect to GlobalProtect intermittently when Enforcer is enabled.
|
||||
|
||||
## GPC-21247
|
||||
|
||||
Fixed an issue where GlobalProtect HIP set the Filevault encryption status to unencrypted on macOS running devices, which denied access to the end-point machines.
|
||||
|
||||
## GPC-21222
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check incorrectly detected the Real Time Protection Status and Last Full Scan for Avast application, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-21206
|
||||
|
||||
Fixed an issue where the GlobalProtect service exited when the user logs off or put the computer in sleep mode.
|
||||
|
||||
## GPC-21174
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check did not detect Real time protection status for Acronis Cyber Protection Agent, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-21130
|
||||
|
||||
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-21106
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP check did not detect Real Time Protection status for Malwarebytes antimalware application, which caused the device to fail the HIP check.
|
||||
|
||||
## GPC-21043
|
||||
|
||||
Fixed an issue where the GlobalProtect app got stuck in connecting stage after authentication when the app was upgraded to 6.2.4 version.
|
||||
|
||||
## GPC-20983
|
||||
|
||||
Fixed an issue where the GlobalProtect app was installed on devices running macOS, the GlobalProtect got stuck in Connecting state when the device woke up from sleep mode.
|
||||
|
||||
## GPC-20967
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed with the Conditional Connect method, users had to click the Connect button twice to connect to an external gateway after a system reboot.
|
||||
|
||||
## GPC-20943
|
||||
|
||||
Fixed an issue where the GlobalProtect enforcer blocked DHCP packets.
|
||||
|
||||
## GPC-20838
|
||||
|
||||
Fixed an issue where the HIP report was not completed within the allowed time.
|
||||
|
||||
## GPC-20807
|
||||
|
||||
Fixed an issue where the HIP report for Symantec Encryption Desktop shows the encryption state as unencrypted.
|
||||
|
||||
## GPC-20779
|
||||
|
||||
Fixed an issue where Windows regional settings were not respected by Webview 2 on SAML embedded browser resulting in regional language(French, German, Chinese, Spanish, and Japanese) not loading properly in embedded browser.
|
||||
|
||||
## GPC-20700
|
||||
|
||||
Fixed an issue where macOS users had to enter the SAML username and password each time they refreshed or rebooted their computer. This issue occurred more frequently when they used Safari as the default browser or used the embedded browser.
|
||||
|
||||
## GPC-20674
|
||||
|
||||
Fixed an issue where all GlobalProtect portals except for the currently connected portal were deleted during the upgrade from 6.2.2 to 6.2.3 or from 6.2.3 to 6.3.0.
|
||||
|
||||
## GPC-20492
|
||||
|
||||
Fixed an issue where the PanGPS process crashed due to exception code 0xC0000374.
|
||||
|
||||
## GPC-20466
|
||||
|
||||
Fixed an issue where the tunnel gets broken during modern standby when using Enforce GlobalProtect for Network Access and the enforcer gets re-enabled only after the user resumes working on the computer.
|
||||
|
||||
## GPC-20441
|
||||
|
||||
Fixed an issue where HIP reports are sometimes not available on the firewall for newly connected users.
|
||||
|
||||
## GPC-20322
|
||||
|
||||
Fixed an issue where users were unable to install GlobalProtect 6.2 on windows 11 ARM64 devices.
|
||||
|
||||
## GPC-20191
|
||||
|
||||
Fixed an issue where the PanGPA executable version 6.1.2.83 did not work as expected on Windows devices.
|
||||
|
||||
## GPC-20168
|
||||
|
||||
Fixed an issue where it was possible to do a privilege escalation and\or login bypass when using a 3rd party credential provider with GlobalProtect.
|
||||
|
||||
## GPC-18943
|
||||
|
||||
Fixed an issue where when Endpoint Traffic enforcement feature was enabled, certain traffic was going through the physical adapter and not getting blocked as per the rules set.
|
||||
|
||||
## GPC-18695
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app version 6.0.7 was installed on devices running macOS, the "Allow with Passcode option did not work as expected when the user tried to disable the GlobalProtect app with the configured passcode.
|
||||
|
||||
## GPC-18671
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS, the GlobalProtect macOS install package created an unused /Library/Application folder.
|
||||
|
||||
## GPC-18452
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on Windows devices, the app did not start right away after a system reboot.
|
||||
@@ -0,0 +1,37 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect
|
||||
version: 6.3.3-h1
|
||||
---
|
||||
|
||||
## GPC-23277
|
||||
|
||||
Fixed an issue where the GlobalProtect macOS client intermittently experienced connection timeouts while browsing the internet in proxy mode (when disconnected from the VPN tunnel). Ping operations were successful, but website access through a browser was slow or failed.
|
||||
|
||||
## GPC-23237
|
||||
|
||||
Fixed an issue where the GlobalProtect macOS client restarted on opening a zoom session in transparent proxy mode.
|
||||
|
||||
## GPC-23215
|
||||
|
||||
Fixed an issue where the traffic stopped passing through the GlobalProtect app on macOS devices after upgrading to GP 6.2.8 and when the computer screen was locked.
|
||||
|
||||
## GPC-23161
|
||||
|
||||
Fixed an issue where the GlobalProtect app stopped working after a session change.
|
||||
|
||||
## GPC-23139
|
||||
|
||||
Fixed an issue where, after a disconnection event, the GlobalProtect agent could not connect to either the transparent proxy or the IPsec tunnel until the client device was rebooted.
|
||||
|
||||
## GPC-23117
|
||||
|
||||
Fixed an issue where after installing GlobalProtect on macOS devices, the host ID displayed the device's MAC address instead of the UID, and the GlobalProtect agent icon flickered.
|
||||
|
||||
## GPC-23077
|
||||
|
||||
Fixed an issue where HIP reports were not sent to the GlobalProtect gateway when transparent proxy is enabled, resulting in rules not being matched.
|
||||
|
||||
## GPC-22777
|
||||
|
||||
Fixed an issue where GlobalProtect entered proxy mode after the computer woke from sleep but failed to apply the configured proxy settings, resulting in a lost proxy connection.
|
||||
@@ -0,0 +1,359 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect
|
||||
version: 6.3.3
|
||||
---
|
||||
|
||||
## GPC-23046
|
||||
|
||||
Fixed an issue where users experienced connectivity problems when GlobalProtect was used in a WiFi network with captive portal.
|
||||
|
||||
## GPC-23010
|
||||
|
||||
Fixed an issue where HIP checks incorrectly detected the macOS built-in firewall as disabled, causing HIP checks to fail.
|
||||
|
||||
## GPC-22847
|
||||
|
||||
Fixed an issue where GlobalProtect did not detect Qualys for patch management.
|
||||
|
||||
## GPC-22771
|
||||
|
||||
Fixed an issue where the Host Information Profile (HIP) check failed to detect the installed version of Norton anti-malware.
|
||||
|
||||
## GPC-22763
|
||||
|
||||
Fixed an issue where GlobalProtect prompted for credentials instead of using authoverride cookie when authenticating to the best available gateway.
|
||||
|
||||
## GPC-22740
|
||||
|
||||
Fixed an issue where macOS computers displayed both the new and old versions of the GlobalProtect welcome page.
|
||||
|
||||
## GPC-22688
|
||||
|
||||
Fixed an issue for proxy-only mode where customers were unable to access websites when the computer woke up from sleep
|
||||
|
||||
## GPC-22638
|
||||
|
||||
Fixed an issue where Global Protect HIP did not detect the drive state when using Trellix Drive Encryption 8.0.
|
||||
|
||||
## GPC-22616
|
||||
|
||||
Fixed an issue where the Digital Guardian Agent was not detected by the GlobalProtect client, causing DLP HIP checks to fail.
|
||||
|
||||
## GPC-22610
|
||||
|
||||
Fixed an issue where, after an upgrade, GlobalProtect restarted and failed to connect to the portal
|
||||
|
||||
## GPC-22589
|
||||
|
||||
Fixed an issue where the Report an Issue functionality did not send the troubleshooting log to the administrator’s Strata Logging Service instance.
|
||||
|
||||
## GPC-22547
|
||||
|
||||
Fixed an issue where the installed OWSPAT version was not supported with the CrowdStrike Falcon version, resulting in HIP object match failures.
|
||||
|
||||
## GPC-22544
|
||||
|
||||
Fixed an issue where the GlobalProtect client did not send the HIP report causing user-IP mapping to be cleared and resulting in traffic drop.
|
||||
|
||||
## GPC-22542
|
||||
|
||||
Fixed an issue where the embedded browser shown as part of SAML authentication was blank.
|
||||
|
||||
## GPC-22487
|
||||
|
||||
Fixed an issue where Norton 360 was not compatible with GlobalProtect causing the device to fail the HIP check.
|
||||
|
||||
## GPC-22450
|
||||
|
||||
Fixed an issue where users were unable to use smartcard authentication with embedded browser.
|
||||
|
||||
## GPC-22448
|
||||
|
||||
Fixed an issue where the GlobalProtect client could crash after it was connected to a gateway.
|
||||
|
||||
## GPC-22443
|
||||
|
||||
Fixed an issue where the GlobalProtect agent showed as connected even when the virtual adapter was down.
|
||||
|
||||
## GPC-22406
|
||||
|
||||
Fixed an issue where the GlobalProtect credential provider was not set as the default after installation and reboot.
|
||||
|
||||
## GPC-22381
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP report did not include Cortex XDR installed on the client machine.
|
||||
|
||||
## GPC-22353
|
||||
|
||||
Fixed an issue where a comment was not visible in the GlobalProtect logs when GlobalProtect was disabled with-comment.
|
||||
|
||||
## GPC-22297
|
||||
|
||||
Fixed an issue where the Customer was getting "A valid client certificate is required for authentication" even though they had a valid client certificate installed.
|
||||
|
||||
## GPC-22295
|
||||
|
||||
Fixed an issue where GlobalProtect client for macOS could not navigate away from a hyperlink on the welcome page when the welcome page was opened in the embedded browser.
|
||||
|
||||
## GPC-22264
|
||||
|
||||
Fixed an issue where the GlobalProtect HIP report did not detect the last full scan time for Avast antivirus software.
|
||||
|
||||
## GPC-22245
|
||||
|
||||
Fixed an issue where transparent upgrade from GlobalProtect version 6.2.4 or 6.2.5 to version 6.2.6 failed on some Windows endpoints with error 1618.
|
||||
|
||||
## GPC-22237
|
||||
|
||||
Fixed an issue where GlobalProtect shut down unexpectedly on Windows 11 devices running multiple versions of GlobalProtect 6.3. The issue was caused by the firewall sending invalid IPv6 packets to GlobalProtect, which did not have a validation method before processing.
|
||||
|
||||
## GPC-22235
|
||||
|
||||
Fixed an issue where users were unable to connect to the app after the system woke up from sleep mode.
|
||||
|
||||
## GPC-22233
|
||||
|
||||
Fixed an issue where the users were unable to connect the GlobalProtect app after performing the resolution of CVE-2024-5921. The app displayed the following error, “The certificate CN name mismatch.”
|
||||
|
||||
## GPC-22155
|
||||
|
||||
Fixed an issue where the GlobalProtect app got stuck in the Connecting stage when the app was upgraded to 6.3.2-525 version. Users had to reboot the system to resolve this issue.
|
||||
|
||||
## GPC-22126
|
||||
|
||||
Fixed an issue where GlobalProtect version 6.2.6-838 was stuck intermittently during the connection process.
|
||||
|
||||
## GPC-22123
|
||||
|
||||
Fixed an issue where the GlobalProtect app got stuck and users faced connection issues after the system woke up from sleep mode even though the internet connection was stable.
|
||||
|
||||
## GPC-22092
|
||||
|
||||
Fixed an issue where the GlobalProtect app failed to validate the server certificate when the portal or gateway sent only the leaf certificate.
|
||||
|
||||
## GPC-22061
|
||||
|
||||
Fixed an issue where the GlobalProtect client displayed an error when using an ECDSA certificate with explicit EC parameters in FIPS mode.
|
||||
|
||||
## GPC-22054
|
||||
|
||||
Fixed an issue where after GlobalProtect was upgraded from version 6.3.0 to 6.3.1, users were stuck in connecting state.
|
||||
|
||||
## GPC-22046
|
||||
|
||||
Fixed an issue where when the GlobalProtect app was installed on devices running macOS and the app version was upgraded to 6.2.5, end users were unable to connect the app. The app got stuck in the Connecting state and displayed the following message, “You are redirected to an embedded browser to authenticate and connect.”
|
||||
|
||||
## GPC-22043
|
||||
|
||||
Fixed an issue where Okta push notification shows incorrect Windows OS, when Okta SAML authentication is enabled in GlobalProtect.
|
||||
|
||||
## GPC-22028
|
||||
|
||||
Fixed an issue where the disconnect reason for macOS users was getting cached.
|
||||
|
||||
## GPC-21988
|
||||
|
||||
Fixed an issue where the GlobalProtect Client displayed a download prompt or was updated even with an "upgrade disallow" configuration.
|
||||
|
||||
## GPC-21960
|
||||
|
||||
Fixed an issue where the HIP check failed to detect the Norton anti-malware version 24.11.9615.0.
|
||||
|
||||
## GPC-21955
|
||||
|
||||
Fixed an issue where the HIP notification pop-up on macOS looked different from that on Windows.
|
||||
|
||||
## GPC-21950
|
||||
|
||||
Fixed an issue where the GlobalProtect connection on MacOS Sequoia 15+ was unstable.
|
||||
|
||||
## GPC-21857
|
||||
|
||||
Fixed an issue where, when the GlobalProtect debug build was installed on the device, the device was immediately locked and users were unable to enter their login credentials in the Window Login screen. Users had to reboot their system to resolve this issue.
|
||||
|
||||
## GPC-21775
|
||||
|
||||
Fixed an issue where GlobalProtect users on macOS were disconnected immediately after sending the HIP report.
|
||||
|
||||
## GPC-21755
|
||||
|
||||
Fixed an issue where GlobalProtect users with enforcer enabled were able to access applications that were not in the enforcer exception list.
|
||||
|
||||
## GPC-21743
|
||||
|
||||
Fixed an issue where a user was randomly prompted with a \"Login Successful\" message when connecting to GlobalProtect (GP), even though GP was not connected.
|
||||
|
||||
## GPC-21737
|
||||
|
||||
Fixed an issue where the SAML redirection page opened up on end user
|
||||
|
||||
computers even though they did not have internet connectivity.
|
||||
|
||||
## GPC-21721
|
||||
|
||||
Fixed an issue, where the GlobalProtect app got stuck in Connecting status when the device woke up from sleep mode.
|
||||
|
||||
## GPC-21695
|
||||
|
||||
Fixed an issue where the GlobalProtect embedded browser could not utilize a new PIV certificate for SAML authentication if multiple certificates were available.
|
||||
|
||||
## GPC-21677
|
||||
|
||||
Fixed an issue where GlobalProtect configured for Always-on Pre-logon may not display the captive portal page if there is a delay with network access or Internet connectivity.
|
||||
|
||||
## GPC-21653
|
||||
|
||||
Fixed an issue where the GlobalProtect virtual adapter was not set up correctly.
|
||||
|
||||
## GPC-21639
|
||||
|
||||
Fixed an issue where the GlobalProtect macOS client did not extend the session even though the user clicked the Extend Session button.
|
||||
|
||||
## GPC-21636
|
||||
|
||||
Fixed an issue where the users were unable to login Windows 11 using the User Principal Name (UPN) when GPCP was selected with GlobalProtect app version 6.2.4 and 'Interactive logon: Don't display last signed-in' was enabled in their Entra ID - group policy.
|
||||
|
||||
## GPC-21627
|
||||
|
||||
Fixed an issue where the Report an Issue feature failed to work for a specific user whose username contained Japanese character.
|
||||
|
||||
## GPC-21615
|
||||
|
||||
Fixed an issue where the GlobalProtect agent (wa_3rd_party_host_64.exe) modified the __PSLockDownPolicy registry key from 4 (secure language mode) to 0 (full language mode) after a reboot.
|
||||
|
||||
## GPC-21583
|
||||
|
||||
Fixed an issue where the change password message was truncated in the GlobalProtect agent UI.
|
||||
|
||||
## GPC-21527
|
||||
|
||||
Fixed an issue where the firewall did not exclude the APIPA (169.254.0.0/16) range from GlobalProtect when the Endpoint Traffic Policy Enforcement feature was enabled with the exclude option. As a result, traffic to the APIPA range was sent over GlobalProtect instead of the local interface.
|
||||
|
||||
## GPC-21482
|
||||
|
||||
Fixed an issue where some users were unable to connect to portal access, the PANGPA did not work as expected and multiple GlobalProtect instances were opened.
|
||||
|
||||
## GPC-21468
|
||||
|
||||
Fixed an issue where HIP reports were not sent during modern standby mode.
|
||||
|
||||
## GPC-21467
|
||||
|
||||
Fixed an issue where the Transparent Upgrade with Proxy only mode did not work as expected and no tunnel was established with the gateway.
|
||||
|
||||
## GPC-21454
|
||||
|
||||
Fixed an issue where GlobalProtect Connect Before Logon connection allowed GlobalProtect to be disconnected on first time login.
|
||||
|
||||
## GPC-21453
|
||||
|
||||
Fixed an issue where the GlobalProtect app window displayed "static" instead of the connected gateway name.
|
||||
|
||||
## GPC-21437
|
||||
|
||||
Fixed an issue where users were unable to connect to Prisma Access via GlobalProtect.
|
||||
|
||||
## GPC-21413
|
||||
|
||||
Fixed an issue where the GlobalProtect Credential Provider did not reset focus on the password field when the user entered the wrong password
|
||||
|
||||
## GPC-21375
|
||||
|
||||
Fixed an issue where username from SAML assertion did not match the config selection criteria because the Windows SSO username was used instead of the SAML username.
|
||||
|
||||
## GPC-21355
|
||||
|
||||
Fixed an issue GlobalProtect pre-logon was stuck in connecting state after a reboot.
|
||||
|
||||
## GPC-21284
|
||||
|
||||
Fixed an issue where the GlobalProtect gateway did not receive the HIP reports from the user correctly due to which the end users were unable to access the resources even when the sessions were active.
|
||||
|
||||
## GPC-21267
|
||||
|
||||
Fixed an issue where, when the user installed the GlobalProtectARM installer from the Customer Support Portal (CSP) and the user opened GlobalProtect using the Start menu, the icon file (PanGPA.ico) was opened instead of the executable (PanGPA.exe) file.
|
||||
|
||||
## GPC-21240
|
||||
|
||||
Fixed an issue where, when the GlobalProtect app was installed on devices running macOS Sonoma 14.5, the app used the old FQDN names and got stuck in the "Connecting" status instead of prompting the user to enter the portal FQDN name.
|
||||
|
||||
## GPC-21161
|
||||
|
||||
Fixed an issue where the notifications for the feature "Login Lifetime Expiration" and "Notify Before Lifetime Expires" were not displayed on the GlobalProtect client running version 6.2.4.
|
||||
|
||||
## GPC-21131
|
||||
|
||||
Fixed an issue where the users were unable to access the Advanced Logging Settings screen of the GlobalProtect app using the ctrl + tab key combination on the keyboard. The screen reader did not announce the Keyboard options correctly.
|
||||
|
||||
## GPC-21090
|
||||
|
||||
Fixed an issue where GlobalProtect only displayed ADEM information for approximately 120 users even though more than 600 ADEM users were connected to GlobalProtect.
|
||||
|
||||
## GPC-21024
|
||||
|
||||
Fixed an issue where a HIP notification configured as "pop-up-message" for pre-logon does not show up. The pop up window is blank.
|
||||
|
||||
## GPC-21005
|
||||
|
||||
Fixed an issue where after submitting the SAML credentials, a blank screen was displayed and GlobalProtect got stuck in that stage.
|
||||
|
||||
## GPC-20992
|
||||
|
||||
Fixed an issue where the Teams application does not connect to the server for macOS.
|
||||
|
||||
## GPC-20991
|
||||
|
||||
Fixed an issue where the Windows Registry value (ext-key-usage-oid-for-client-cert) on \HKEY_LOCAL_MACHINE\SOFTWARE\Palo Alto Networks\GlobalProtect\Settings was deleted during the upgrade from GlobalProtect version 6.2.2 to version 6.2.4. This makes the GlobalProtect client unable to select a certificate by itself.
|
||||
|
||||
## GPC-20977
|
||||
|
||||
Fixed an issue where conditional connect was not set and GlobalProtect connected to an external gateway on the internal network instead of connecting to an internal gateway on the internal network.
|
||||
|
||||
## GPC-20813
|
||||
|
||||
Fixed an issue where GlobalProtect 6.3.0 on macOS was blocking multicast traffic on the local network interface.
|
||||
|
||||
## GPC-20783
|
||||
|
||||
Fixed an issue where, when the embedded browser was used, the password field did not work as expected when users typed their passwords in the field. Users had to click inside the password field before entering their password.
|
||||
|
||||
## GPC-20736
|
||||
|
||||
Fixed an issue where users are being logged out from GlobalProtect when the device wakes up from modern standby and network discovery happens.
|
||||
|
||||
## GPC-20632
|
||||
|
||||
Fixed an issue where GLobalProtect was stuck in connecting mode after the customer manually selected a gateway that hit the maximum user limit. This was a multi-gateway environment with SAML/CAS authentication method.
|
||||
|
||||
## GPC-20550
|
||||
|
||||
Fixed an issue where Zoom and Outlook apps intermittently stop connecting on macOS with an error "You are unable to connect to Zoom. Please check your network connection and try again" when the apps are excluded under both domains and applications
|
||||
|
||||
## GPC-20514
|
||||
|
||||
Fixed an issue where the remote users using GlobalProtect with Connect Before Logon (CBL) were unable to reset their password when using the app with an embedded browser.
|
||||
|
||||
## GPC-20461
|
||||
|
||||
Fixed an issue where the GlobalProtect agent version 6.1.4 would only establish a connection via SSL to an IPv6 gateway. The IPSec tunnel was not established or connected.
|
||||
|
||||
## GPC-20416
|
||||
|
||||
Fixed an issue where there is no network discovery once the laptop came out of standby.
|
||||
|
||||
## GPC-20386
|
||||
|
||||
Fixed an issue where Windows users experienced a blue screen of death issue due to a race condition between Microsoft IPSEC extension and GlobalProtect. The issue happens only when IKE extensions are enabled via IPSEC GPO on the endpoint along with GlobalProtect.
|
||||
|
||||
## GPC-20292
|
||||
|
||||
Fixed an issue where the Azure VDI RDP connection disconnects when using enforcer.
|
||||
|
||||
## GPC-20168
|
||||
|
||||
Fixed an issue where it was possible to do a privilege escalation and\or login bypass when using a 3rd party credential provider with GlobalProtect
|
||||
|
||||
## GPC-18106
|
||||
|
||||
Fixed an issue where the GlobalProtect app intermittently did not send the HIP report to the Prisma Access gateway due to a timeout issue.
|
||||
Reference in New Issue
Block a user