Filter

Expand All | Collapse All

Prisma Agent Docs

Administration
User Guide
Release Notes

Focus

Prisma Agent

Prisma Agent 25.3.0 (Mobile) Known Issues

Table of Contents

Prisma Agent 25.4 Known Issues

Prisma Agent 25.3.1 Known Issues

Prisma Agent 25.3.0 (Mobile) Known Issues

Review the known issues in Prisma Agent mobile version 25.3.0.

Prisma Agent mobile versions 25.3.0 (iOS) and 25.3.0.11 (Android) have the following known issues:

Issue ID	Description
PANG-8284	An issue exists where the Prisma Agent on Android and iOS devices does not enforce the session timeout settings configured in the Agent configuration. When you configure specific session timeout values in your Agent settings, the Android and iOS agents fail to apply these predetermined timeout intervals and will use the default timeout value.
PANG-8283	An issue exists where the embedded browser cookies are not cleared when users sign out of the Prisma Agent on Android devices that use the embedded browser for SAML authentication. When a user signs out of the agent, the system fails to properly clear the stored authentication cookies within the embedded browser, potentially leaving residual session data.
PANG-8282	Prisma Agent on Android does not support IPSec connectivity when deployed in NGFW deployments. The agent will automatically detect this unsupported configuration and fall back to SSL connectivity to maintain proper functionality.
PANG-8223	An issue exists where the Prisma Agent on iOS and Android allows users to sign out even when the Allow User to Sign Out Agent Setting is disabled. When you configure the agent to prevent users from signing out through the agent settings, the Prisma Agent app continues to display an active sign-out option that successfully logs the user out when selected.
—	An issue exists where automatic tunnel restoration for on-demand connections on Android and iOS, Android, and ChromeOS devices requires manual user intervention when switching between Wi-Fi networks. When on-demand connectivity is configured and an end user transitions from one Wi-Fi network to another, the agent detects the network change but does not automatically re-establish the tunnel connection without user action. The user must tap Connect to establish connectivity with the Prisma Agent.
—	Internal Host Detection is currently not supported on Android and iOS devices. When you deploy Prisma Agents on iOS, Android, and ChromeOS platforms, the agents cannot automatically detect or identify whether the device is within in your network environment, limiting the agent's ability to make routing decisions based on internal network topology.
—	An issue exists where end users are unable to switch locations when using Prisma Agent on an iPad device. This restricts the users' ability to optimize connection performance or access region-specific resources. Users will only be able to connect to the best available location.

Prisma Agent 25.4 Known Issues

Prisma Agent 25.3.1 Known Issues