Added rest of GP 6.3 addressed issues
This commit is contained in:
@@ -0,0 +1,45 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: GlobalProtect
|
||||
version: 6.3.3-h6
|
||||
---
|
||||
|
||||
## GPC-24683
|
||||
|
||||
Fixed an issue where Host Information Profile (HIP) matching failed for Anti-Malware criteria on macOS endpoints due to GlobalProtect failing to detect the virus definition version for Kaspersky Anti-Virus.
|
||||
|
||||
## GPC-24579
|
||||
|
||||
Fixed an issue where GlobalProtect clients were unable to authenticate to internal gateways when multiple internal gateways were configured. This issue occured because the GlobalProtect client did not properly reset the SAML login flag, causing subsequent SAML pre-login requests to be ignored.
|
||||
|
||||
## GPC-24548
|
||||
|
||||
Fixed an issue where macOS GlobalProtect (GP) clients connected to an internal gateway with the enforcer enabled were unable to access the internet via a proxy. This occurred because the tunnel_connected flag remained set to 1 after the gateway disconnected, even though the gateway configuration was cleared.
|
||||
|
||||
## GPC-24261
|
||||
|
||||
Fixed an issue where GlobalProtect app running on macOS Sequoia 15.6.1 running GP 6.2.8 -c263 that receive both IPv4 and IPv6 addresses were not receiving packets back from the Network Load Balancer (NLB) instances.
|
||||
|
||||
## GPC-24221
|
||||
|
||||
Fixed an issue where the GlobalProtect app experienced a continuous connect-disconnect loop when used on flights. This issue occurred because rapid network wake-ups left network interfaces in an inconsistent state, causing GlobalProtect to attempt tunnel establishment on an unstable network foundation.
|
||||
|
||||
## GPC-24103
|
||||
|
||||
Fixed an issue where the GlobalProtect app running on macOS allowed users to modify or add a new portal address after each device reboot, even when the "Allow users to change portal" setting was configured as "No" in the GlobalProtect app.
|
||||
|
||||
## GPC-24037
|
||||
|
||||
Fixed an issue where GlobalProtect app prompted users to log in with SAML through the embedded browser even when the GlobalProtect app was already connected. This occurred when users logged off and then back onto their Cloud PC (Windows Azure PC), and closing the prompt disconnected and reconnected the VPN session.
|
||||
|
||||
## GPC-23929
|
||||
|
||||
Fixed an issue where, when GlobalProtect app was configured with Enforcer, users could bypass Enforcer restrictions by repeatedly canceling authentication prompts after logging into Windows. This occurred because the cached portal configuration, which contains Enforcer settings, was not loaded when a pre-logon tunnel failed to establish due to a quick user login. This fix ensures that the cached portal configuration is loaded as soon as PanGPA starts and PanGPS learns the username, preventing unrestricted access in scenarios where Enforcer is intended to lockdown the endpoint.
|
||||
|
||||
## GPC-23394
|
||||
|
||||
Fixed an issue where GlobalProtect app version 6.2.8-183. running on macOS 15.5 was unable to accurately report the disk encryption status of FileVault, resulting in an "unknown" status in HIP checks.
|
||||
|
||||
## GPC-22797
|
||||
|
||||
Fixed an issue where the MAC address generated for the DHCP feature changed on every GlobalProtect client restart. The MAC address should remain static after initial generation to allow static IP assignment on the DHCP server side for a specific GlobalProtect client. Additionally, the generated MAC address was not always marked as unicast and locally administered.
|
||||
Reference in New Issue
Block a user