Prisma Access Agent
Prisma Access Agent Known Issues
Table of Contents
Expand All
|
Collapse All
Prisma Access Agent Docs
-
-
- Configure the Prisma Access Agent (Coexistence Tenant)
- Set Up the Infrastructure for Prisma Access Agents
- Configure General Global Settings for the Prisma Access Agent
- Configure a Certificate to Decrypt the Authentication Override Cookie (Panorama Managed NGFW)
- Export the Authentication Override Cookie for Connecting to an On-Premises NGFW Gateway (Coexistence Tenant)
- Push the Prisma Access Agent Configuration
-
- Prisma Access Agent Overview
-
- Install the Prisma Access Agent
- Log in to the Prisma Access Agent
- Change Prisma Access Agent App Settings
- Connect the Prisma Access Agent to a Different Location
- Connect the Prisma Access Agent to a Different Server
- View Prisma Access Agent Notifications
- Disconnect the Prisma Access Agent from a Location
- Disable the Prisma Access Agent
- Log out of the Prisma Access Agent
- Get Help for Prisma Access Agent Issues
- Switch Between the Prisma Access Agent and GlobalProtect App
- Prisma Access Agent Commands
Prisma Access Agent Known Issues
Review the known issues for the Prisma Access Agent.
| Where Can I Use This? | What Do I Need? |
|---|---|
|
For Prisma Access deployments:
For NGFW deployments:
For all deployments:
|
The Prisma Access Agent has the following known issues.
| Issue ID | Description |
|---|---|
| PANG-6738 |
An issue exists where certificate authentication fails on Windows
devices when certificates are stored in the machine certificate
store. This impacts Prisma Access Agent functionality for Windows
users attempting to authenticate using machine-level
certificates.
Workaround: Import the client certificate from the machine
store to the user's personal certificate store. The Prisma Access
Agent is able to recognize and use client certificate credentials
when they are located in the user store, even if it can’t access
them in the machine store.
|
| EPM-4848 |
As ring mappings for Prisma Access Agents are calculated during
configuration time, the ring mappings might not always be accurate.
Some potential causes are new agent enrollments, changes in
directory binding, or host operating system updates.
Workaround: Before initiating a staged upgrade rollout of the
agent, perform a commit push. This action ensures all agents are
correctly mapped to their designated upgrade rings. If new agents
are enrolled after you run the commit push, the new agents are
always mapped to the default ring until the next commit push.
|
| EPM-4821 |
The ConnectPre-logon option is present in the Prisma Access Agent Settings
page for Panorama Managed Prisma Access and NGFW deployments, even
though it's not functional.
Workaround: Ignore this option as it won’t work.
|
| EPM-4616 |
An issue exists where newly added internal gateways are not visible
in existing Prisma Access Agent settings. This affects the ability
to update agent configurations with recently added internal
gateways.
This occurs when you select WorkflowsPrisma Access AgentSetupPrisma Access Agent and create an agent setting with external and
internal gateways. Then, if you add additional internal gateways
from the Infrastructure page, the added internal gateways don't
appear in the previous agent setting.
Workaround: Create a new agent setting to see and utilize the
newly added internal gateways.
|
If you need to view the known issues for the Dynamic Privilege Access enabled Prisma Access Agent, see “Known Issues for Dynamic Privilege Access” in Prisma Access Known Issues.