Add GP 6.3 known issues
This commit is contained in:
@@ -0,0 +1,55 @@
|
||||
---
|
||||
type: Known
|
||||
product: GlobalProtect
|
||||
version: 6.3.3-h3
|
||||
---
|
||||
|
||||
## 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-23149
|
||||
|
||||
Connection via captive portal does not work in agent proxy mode when the captive portal is hosted on a non-local network.
|
||||
|
||||
## GPC-21982
|
||||
|
||||
IPv6 traffic on the Windows client does not follow the routing table and leaks through the physical adapter.
|
||||
|
||||
## GPC-21694
|
||||
|
||||
When the GlobalProtect app is installed on Windows, a Microsoft Defender SmartScreen warning is displayed:.
|
||||
|
||||
**Workaround:**Click More Info and then click Run to proceed with the installation.
|
||||
|
||||
## GPC-21558
|
||||
|
||||
When the GlobalProtect app is installed on devices running on macOS and the end user enable or disable the system extensions, the GlobalProtect Enforcer feature is not working as expected.
|
||||
|
||||
## GPC-20840
|
||||
|
||||
Loading content or text on the SAML embedded browser can take longer than usual. This does not impact authentication.
|
||||
|
||||
## GPC-17513
|
||||
|
||||
When GlobalProtect is configured in [Tunnel and Proxy mode](https://docs.paloaltonetworks.com/prisma-access/administration/prisma-access-mobile-users/mobile-users-explicit-proxy/agent-based-proxy-globalprotect-tunnel-and-proxy-mode) or [proxy mode](https://docs.paloaltonetworks.com/prisma-access/administration/prisma-access-mobile-users/mobile-users-explicit-proxy/agent-based-proxy-globalprotect-proxy-mode), if the admin-defined PAC file has an HTTP URL, the GlobalProtect app will not download the PAC content.
|
||||
|
||||
## GPC-17447
|
||||
|
||||
When the GlobalProtect app is configured in [Tunnel and Proxy mode](https://docs.paloaltonetworks.com/prisma-access/administration/prisma-access-mobile-users/mobile-users-explicit-proxy/agent-based-proxy-globalprotect-tunnel-and-proxy-mode), SSL VPN establishment over the proxy doesn't work.
|
||||
|
||||
## GPC-17663
|
||||
|
||||
In [Tunnel and Proxy mode](https://docs.paloaltonetworks.com/prisma-access/administration/prisma-access-mobile-users/mobile-users-explicit-proxy/agent-based-proxy-globalprotect-tunnel-and-proxy-mode), the GlobalProtect agent tunnel does not work seamlessly when the GlobalProtect app and the third-party VPN are configured to use overlapping IP subnets.
|
||||
|
||||
**Workaround:** Use GlobalProtect in [proxy mode](https://docs.paloaltonetworks.com/prisma-access/administration/prisma-access-mobile-users/mobile-users-explicit-proxy/agent-based-proxy-globalprotect-proxy-mode) for better compatibility with third-party VPNs.
|
||||
|
||||
## GPC-17555
|
||||
|
||||
In [Tunnel and Proxy mode](https://docs.paloaltonetworks.com/prisma-access/administration/prisma-access-mobile-users/mobile-users-explicit-proxy/agent-based-proxy-globalprotect-tunnel-and-proxy-mode), the GlobalProtect agent tunnel on macOS does not coexist well with Cisco Anyconnect VPN due to an IP forwarding table issue.
|
||||
|
||||
**Workaround:** Use GlobalProtect in [proxy mode](https://docs.paloaltonetworks.com/prisma-access/administration/prisma-access-mobile-users/mobile-users-explicit-proxy/agent-based-proxy-globalprotect-proxy-mode) for better compatibility with third-party VPNs.
|
||||
|
||||
## GPC-17854
|
||||
|
||||
The GlobalProtect app does not prompt the users to extend the login lifetime user session when the device woke up from sleep or hibernation mode.
|
||||
Reference in New Issue
Block a user