99 lines
3.9 KiB
Markdown
99 lines
3.9 KiB
Markdown
---
|
|
type: Known
|
|
product: Prisma Access Agent
|
|
version: 25.6
|
|
---
|
|
|
|
## PANG-9334
|
|
|
|
An issue exists where the Prisma Access Agent user interface is cut
|
|
off or displayed incorrectly on macOS 26 (Tahoe). Users running the
|
|
this macOS version may experience visual rendering problems with the
|
|
Prisma Access Agent application, where portions of the interface
|
|
elements, menus, or dialog boxes are truncated or not properly
|
|
displayed within the application window. This display issue can
|
|
impact user interaction with the agent's configuration settings,
|
|
status information, and other UI components, potentially making it
|
|
difficult to use the Prisma Access Agent functionality.
|
|
|
|
## PANG-9282
|
|
|
|
An issue exists where the Prisma Access Agent's embedded browser
|
|
throws a "Server Error" dialog when users attempt to sign into the
|
|
Prisma Access Agent Manager (EPM) server using Windows Hello PRT
|
|
(Primary Refresh Token) authentication. This problem occurs
|
|
specifically on Windows machines that are Active Directory-joined
|
|
and have Windows Hello PIN configured. When users successfully
|
|
authenticate to their laptop using Windows Hello PIN and
|
|
subsequently try to access the EPM server through the Prisma Access
|
|
Agent, the embedded browser fails to properly handle the Primary
|
|
Refresh Token authentication flow, resulting in a "Server Error"
|
|
dialog instead of successful authentication.
|
|
|
|
## PANG-9242
|
|
|
|
```resolved
|
|
Resolved in Prisma Access Agent 25.7
|
|
```
|
|
|
|
An issue exists where the Prisma Access Agent fails to remove the
|
|
tunnel interface from the routing table when executing the
|
|
pacli epm signout command after the
|
|
gateway has been shut down and the agent is in a
|
|
Disconnected state. This issue affects
|
|
Prisma Access Agents on macOS and Windows, and occurs when the agent
|
|
was previously connected to a tenant but transitions to a
|
|
disconnected state due to gateway shutdowns.
|
|
|
|
When users attempt to sign out using the pacli
|
|
command, the signout appears successful and the EPM status shows as
|
|
Down with Not
|
|
Enrolled authentication status, however the tunnel
|
|
interface and associated routing table entries remain active in the
|
|
system. This results in orphaned network routes that should have
|
|
been cleaned up during the signout process, potentially causing
|
|
network connectivity issues.
|
|
|
|
## PANG-8929
|
|
|
|
```resolved
|
|
Resolved in Prisma Access Agent 25.7
|
|
```
|
|
|
|
An issue exists where the Prisma Access Agent on Windows reports
|
|
error: 513 - PASrv is unreachable, please confirm
|
|
it's running when executing the pacli epm
|
|
status command, even though the PASrv service is
|
|
confirmed to be running in both Task Manager and service control
|
|
manager queries.
|
|
|
|
This issue occurs specifically during a reinstallation scenario where
|
|
the agent is first installed and connects successfully, then
|
|
uninstalled, and subsequently reinstalled. After the second
|
|
installation, while the agent appears to connect normally, the
|
|
pacli command line interface fails to
|
|
communicate with the PASrv service, generating the unreachable
|
|
service error. Additionally, when users attempt to sign out from the
|
|
UI and reconnect, the embedded browser successfully completes
|
|
authentication with the identity provider, but the agent becomes
|
|
stuck in a "connecting" state and fails to establish a proper
|
|
connection.
|
|
|
|
Workaround: Manually restarting the PASrv service, which
|
|
restores normal agent functionality and allows proper communication
|
|
between the pacli interface and the
|
|
service.
|
|
|
|
## ADI-49478
|
|
|
|
An issue exists where the Strata Cloud Manager displays an
|
|
ADNS option under the forwarding profiles
|
|
setup in the connectivity object configuration, even though ADNS
|
|
support is not available in current Prisma Access Agent releases.
|
|
The ADNS option appears as disabled by default in the user
|
|
interface, but since the underlying functionality is not yet
|
|
implemented in the agent software, this configuration option should
|
|
not be used. Administrators encountering this option in Strata Cloud
|
|
Manager should ignore it until proper agent support is implemented
|
|
in future releases.
|