>
    Prisma Access Addressed Issues
    Focus
    Download PDF
    Focus
    1. Home
    2. Prisma Access
    3. Prisma Access Release Information
    4. Prisma Access Addressed Issues
    Download PDF
    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)
    • Prisma Access license
    • Minimum Required Prisma Access Version 5.1 Preferred or Innovation
    The following topics describe issues that have been addressed in Prisma Access 5.1.

    Prisma Access 5.1.1 Addressed Issues

    Issue IDDescription
    CYR-42364Fixed an issue where the PAC file upload failed if there were any upper case letter in the Explicit Proxy URL.
    CYR-42191Fixed 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.

    Prisma Access 5.1.0-h32 Addressed Issues

    Issue IDDescription
    CYR-45874Fixed an issue where, in a Panorama managed multitenant mobile user deployment, enabling ADEM prevented local commits from being successful.
    CYR-45143Fixed an issue where CloudBlade integrations were not working in FedRAMP high and FedRAMP moderate environments.
    CYR-45112Fixed an issue where the external gateway configuration was grayed out when upgrading the Cloud Services plugin to versions 5.1.0 or later.
    CYR-43673Fixed an issue where all the invalid configurations from the API were relayed back to the system administrator via a GET call.
    CYR-43473Fixed an intermittent issue where nsupdate records were not properly deleted from the DNS server for some endpoints configured with the Pre-Logon connect method.

    Prisma Access 5.1.0-h26 Addressed Issues

    Issue IDDescription
    CYR-44598Fixed an issue where the Strata Logging Service status for Panorama Managed Prisma Access deployments was displaying an Exception customer-id error.
    CYR-44354Fixed an issue where a Prisma SD-WAN CloudBlade Version 4.0.0 stopped working without a proxy.

    Prisma Access 5.1.0-h21 Addressed Issues

    Issue IDDescription
    CYR-43562Fixed an issue where the export of current users from the status page has:
    • Correct hostnames in the CSV2.
    • Computer name in the CSV3.
    • Fixed formatting errors in the CSV.
    CYR-43502
    Fixed an issue where, during a Commit and Push operation, some invalid Prisma Access configurations were validates successfully in Panorama, but were not successfully pushed due to errors in the cloud-based infrastructure.

    Prisma Access 5.1.0-h15 Addressed Issues

    Issue IDDescription
    CYR-43237Fixed an issue where Panorama Managed Prisma Access deployments that use proxies did not work with Prisma SD-WAN deployments using Prisma Access CloudBlade Integration Release 4.0.0.
    CYR-43132
    Fixed an issue where, during sub-tenant creation on Panorama, the user could not configure units for either Remote Networks or Mobile Users. You can now configure both units at the same time.
    CYR-42787Fixed an issue where the sub-tenant summary was missing on the Panorama Status page when the response from the Prisma Access backend was not fetched successfully.
    CYR-42499Fixed an issue where, in a new multitenant deployment that didn't have any existing configuration, administrators were not allowed to enter the sub-tenant name manually.
    CYR-42146IP Optimization has the following caveats for IPv6:
    • If you have IP Optimization enabled, you cannot configure IPv6.
    • If you have IPv6 enabled, you cannot enable IP Optimization.
    Workaround: If you have IP Optimization enabled, make sure that you have not enabled IPv6 and, if it is enabled, disable it in Workflows > Prisma Access SetupPrisma Access (in Strata Cloud Manager) or PanoramaCloud ServicesConfigurationService Setup (in Panorama).

    Prisma Access 5.1.0 Addressed Issues

    Issue IDDescription
    CYR-41084Fixed an issue where, after disabling the Cloud Identity Engine integration with Prisma Access, existing Group Mapping Settings caused an error upon commit.
    CYR-39907Fixed an issue where, if you enabled IP Optimization for a Panorama Managed Prisma Access deployment, EDL-related information in the Troubleshooting Commands area (PanoramaCloud ServicesConfigurationService SetupService OperationsTroubleshooting Command) did not work.
    CYR-39874Fixed an issue where an Explicit Proxy template was created without Explicit Proxy being onboarded, which caused an issue when Explicit Proxy was onboarded later.
    CYR-39599Fixed an issue where some columns in the Egress IP Allowlist table displayed that were related to IPv6, even though the IPv6 feature has not been enabled.
    CYR-39553Fixed an issue where the Autonomous DEM AIOps Allocated Total number was incorrect for multitenant setups.
    CYR-39510Fixed an issue where users were not able to onboard and configure Colo-Connect in the Saudi Arabia location.
    CYR-38500Fixed an issue where the France North was displaying as a supported Explicit Proxy location.
    CYR-38418Fixed an issue where, after enabling IPv6, a Prisma Access dataplane upgrade from 10.2.8-h1 to 10.2.8-h2 failed.
    CYR-38386Fixed an issue where, after an autoscaling operation caused more Mobile User gateways to be created, a Commit and Push operation failed.
    CYR-38318Fixed an issue where the Withdraw Static Routes if Service Connection or Remote Networks IPSec tunnel is down choice was enabled by default and not configurable.
    CYR-38131Fixed an issue where, if you had an existing Prisma Access deployment and you upgraded your deployment to the 10.2.8 dataplane, you could not use App Acceleration with existing IPSec termination nodes, which meant that you could not use App Acceleration with existing remote networks after a dataplane upgrade to 10.2.8.
    CYR-37913Fixed 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-36930Fixed 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-36455Fixed an issue where, if a push operation push failed in the Managed Cloud WAN configuration, the job was viewed as Success.

    © 2024 Palo Alto Networks, Inc. All rights reserved.