Remove dates from issue filenames
This commit is contained in:
@@ -0,0 +1,38 @@
|
||||
---
|
||||
type: Known
|
||||
product: Prisma Access Agent
|
||||
version: 25.3
|
||||
---
|
||||
|
||||
## PANG-7865
|
||||
|
||||
```resolved
|
||||
Resolved in Prisma Access Agent 25.4
|
||||
```
|
||||
|
||||
An issue exists where the Prisma Access Agent on Windows does not
|
||||
properly honor updated session timers after a user extends their
|
||||
session through the embedded browser.
|
||||
|
||||
When a user clicks on the session expiry banner displayed in the
|
||||
Prisma Access Agent app, the embedded browser opens and enables the
|
||||
user to authenticate, successfully extending the Prisma Access Agent
|
||||
Manager (EPM) session with a new expiration time. However, the
|
||||
Prisma Access Agent continues to use the original session expiration
|
||||
timer instead of adopting the newly extended session duration.
|
||||
|
||||
As a result, when the original session timer expires, Prisma Access
|
||||
Agent incorrectly terminates the EPM session despite the successful
|
||||
extension. Additionally, the Prisma Access Agent icon becomes
|
||||
unresponsive in the system tray after this occurs.
|
||||
|
||||
## PANG-7012
|
||||
|
||||
```resolved
|
||||
Resolved in Prisma Access Agent 25.3.1
|
||||
```
|
||||
|
||||
An issue exists where the embedded browser for Prisma Access Agent
|
||||
does not reuse the Windows Hello token for reauthentication. As a
|
||||
result, users are required to manually enter their credentials even
|
||||
when Windows Hello is enabled on their devices.
|
||||
Reference in New Issue
Block a user