Prisma Access Addressed Issues
Focus
Focus
Prisma Access

Prisma Access Addressed Issues

Table of Contents

Prisma Access Addressed Issues

Where Can I Use This?
What Do I Need?
  • Prisma Access (Managed by Panorama)
  • Minimum Required Prisma Access Version
    5.2 Preferred or Innovation
The following topics describe issues that have been addressed in Prisma Access 5.2.

Prisma Access 5.2.0 Addressed Issues

Issue ID
Description
CYR-45112
Fixed an issue where the external gateway configuration was grayed out when upgrading the Cloud Services plugin to versions 5.1.0 or later.
CYR-44598
Fixed an issue where the Strata Logging Service status for Panorama Managed Prisma Access deployments was displaying an
Exception
<customer-id>
error.
CYR-43673
Fixed an issue where all the invalid configurations from the API were relayed back to the system administrator via a GET call.
CYR-43400
Fixed an issue where, for connectors onboarded in ZTNA connector groups with
Preserve User ID
checked,
Actions
Diagnostics
ping
from the internal interface to the data center apps did not work.
CYR-43280
Fixed an issue where an illegal base64 data error caused the DSP to fail to generate a diff, even though changes were present.
CYR-43262
Fixed an issue where remote network API requests for Remote Network onboarding threw a commit validation error in the plugin when BGP configuration was included in the payload.
CYR-43222
Fixed an issue where application targets assigned to User ID-based ZTNA Connector groups did not support a
Probing Type
of
icmp ping
.
CYR-42377
Fixed an issue where, when configuring Dynamic DNS Registration Support for Remote Troubleshooting and Updates, an unencrypted Kerberos key file could not be uploaded on the Panorama that manages Prisma Access when the
Authentication Type
was
Kerberos
.
CYR-42191
Fixed an issue where, when setting up Dynamic DNS Support, a valid Kerberos file was not correctly uploaded and was not saved in the system configuration.
CYR-41740
Fixed an issue where, if there were more than 100 connectors onboarded in the same region in a short duration of time, private app access through some of the ZTNA connectors might not work.
CYR-38418
Fixed an issue where, after enabling IPv6, a Prisma Access dataplane upgrade from 10.2.8-h1 to 10.2.8-h2 failed.
CYR-38386
Fixed an issue where, after an autoscaling operation caused more Mobile User gateways to be created, a Commit and Push operation failed.
CYR-37913
Fixed an issue where, if you disabled traffic replication in a compute and re-enabled it in the same compute, the traffic replication functionality was impacted, and you did not see any mobile user or remote network traffic replicated with no no commit or configuration failures displayed.
CYR-37791
Fixed an issue where, after a user switched from one project to another and connected to the same Prisma Access location, the Monitor > Users page in Strata Cloud Manager did not reflect the correct project name that the user switched to for the following time ranges: 3 hours, 24 hours, 7 days, and 30 days.
CYR-36930
Fixed an issue where, if a GlobalProtect mobile user had dual stack (IPv4 and IPv6) enabled and they connected to a Prisma Access GlobalProtect location that had IPv6 enabled and IPv6 was later disabled for that location, the dual-stack user could not connect to that location.
CYR-27734
Fixed an issue where the Policy Optimizer for unused Rule usage statistics were not visible in Panorama for remote network device groups.

Recommended For You