Add Prisma Access Agent known and addressed issues
This commit is contained in:
@@ -0,0 +1,51 @@
|
||||
---
|
||||
type: Addressed
|
||||
product: Prisma Access Agent
|
||||
version: 25.4
|
||||
---
|
||||
|
||||
## PANG-7949
|
||||
|
||||
Fixed an issue where the Dynamic Privilege Access enabled Prisma
|
||||
Access Agent was unable to connect to a gateway after upgrading an
|
||||
endpoint to Windows 11 24H2. Following the Windows upgrade, the
|
||||
Prisma Access Agent would lose the ability to establish gateway
|
||||
connections, even though the Endpoint Manager (EPM) connection
|
||||
remained functional. This issue occurred consistently across systems
|
||||
that had undergone the Windows 11 24H2 upgrade, affecting the
|
||||
agent's ability to connect to any configured gateways while
|
||||
maintaining normal endpoint manager connectivity.
|
||||
|
||||
## PANG-7865
|
||||
|
||||
Fixed an issue where the Prisma Access Agent on Windows did not
|
||||
properly honor updated session timers after a user extended their
|
||||
session through the embedded browser. The agent now correctly adopts
|
||||
the newly extended session duration when users authenticate through
|
||||
the session expiry banner, preventing premature session termination
|
||||
and ensuring the Prisma Access Agent icon remains responsive in the
|
||||
system tray throughout the extended session period.
|
||||
|
||||
## PANG-7960
|
||||
|
||||
Fixed an issue where the Prisma Access Agent on Windows blocked
|
||||
authentication in the embedded browser due to the
|
||||
Best Available - Fail Safe mechanism
|
||||
in the forwarding profile triggering during the initial
|
||||
connection attempt. The embedded browser now properly bypasses
|
||||
the fail-safe mechanism when the agent is configured to run in
|
||||
on-demand mode, enabling successful authentication on the first
|
||||
attempt without requiring users to cancel and retry the
|
||||
authentication process after a reboot.
|
||||
|
||||
## PANG-7309
|
||||
|
||||
Fixed an issue where the Prisma Access Agent on Windows failed to
|
||||
automatically switch from an external gateway to an internal gateway
|
||||
when the user's device woke from sleep mode after being connected to
|
||||
different network environments. The agent now properly detects
|
||||
network changes upon waking from sleep. It also automatically
|
||||
switches to the appropriate internal gateway without requiring
|
||||
manual sign-out via the pacli epm signout
|
||||
command and subsequent reauthentication through the Prisma Access
|
||||
Agent app.
|
||||
Reference in New Issue
Block a user