Add Prisma Access Agent known and addressed issues

2026-03-16 21:35:47 -05:00
parent f1e49c5830
commit 70dcd896be
25 changed files with 1054 additions and 0 deletions
@@ -0,0 +1,54 @@
+---
+type: Addressed
+product: Prisma Access Agent
+version: 26.1.2
+---
+
+## PANG-11395
+
+Fixed an issue where the Prisma Access Agent on Windows 11
+laptops did not reauthenticate with the internal gateway when
+transitioning between network interfaces (for example, from
+Wi-Fi to LAN) and temporarily having more than one active
+network interface. This prevented the IP-user mapping from being
+updated on the NGFW firewall, causing traffic from the user's IP
+to be unrecognized.
+
+## PANG-11328
+
+Fixed an issue where DNS resolution failed for Microsoft 365
+services (MS Teams and Outlook) running Prisma Access Agents on
+dual-stack Windows devices.
+
+## PANG-11311
+
+Fixed an issue where the Prisma Access Agent displayed an
+erroneous "Your connectivity might be affected. Please try again
+or contact your administrator" error notification when a user
+manually disconnected from an on-demand connection.
+
+## PANG-11293
+
+Fixed an issue where Prisma Access Agent version 26.1 was unable
+to retrieve the status of disk encryption for Host Information
+Profile (HIP) reports, causing HIP checks to fail and denying
+access to private applications.
+
+## PANG-11284
+
+Fixed an issue where, after upgrading to Prisma Access Agent
+version 26.1.1.10 on Windows, users attempting to log in with
+Microsoft Entra SSO experienced login failures and HIP check
+compliance errors (Error 53000) because the embedded browser
+incorrectly prompted for a plugin installation."
+
+## PANG-11274
+
+Fixed an issue on macOS devices where gateway connections would
+fail or experience significant delays after waking from sleep.
+This occurred because the Prisma Access Agent service (daemon)
+attempted to access client certificates in the login keychain
+through the user interface (UI) while the UI was still asleep.
+These requests would queue up and process sequentially once the
+UI woke, causing older requests to time out and preventing
+timely gateway connections.