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 6.0 Preferred or Innovation
The following topics describe issues that have been addressed in Prisma Access 6.0 and Prisma Access 6.0.

Prisma Access 6.0.1 Addressed Issues

Issue IDDescription
CYR-41740Fixed 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.

Prisma Access 6.0.0-h22 Addressed Issues

Issue IDDescription
CYR-55537Fixed an issue related to search fields in remote network, service connection, and mobile user templates for the Zones tab.
CYR-55228Fixed an issue where, after a bulk import of remote networks using a .csv file, a commit failure was encountered.
CYR-55216Fixed an issue where the a commit-all operation failed for a Hybrid-SWG device or platform that doesn't support the Cloud Services plugin.
CYR-55138Fixed an issue where the Aggregate Bandwidth widget was not being displayed for remote networks in the Cloud Services plugin.
CYR-54543Fixed an issue where Panorama-based forced GlobalProtect logout was failing when a logged in user had a special character in the user name or computer name. You can now have a successfully log out users or computers that have a special character in the username or computer name using the logout button on the panorama plugin for Prisma Access.
CYR-54428Fixed an issue related to the Service Connection Device Group Template Stack.
CYR-53485Fixed an issue where a GlobalProtect app log certificate, which is required for ADEM, could not be generated for Prisma Access China.

Prisma Access 6.0.0-h11 Addressed Issues

Issue IDDescription
CYR-55020Fixed an issue where the Cloud Services plugin did not display the Remote Networks and Mobile Users configuration.
CYR-49944Fixed an issue where a secondary DNS server was configured, which should not be allowed.
CYR-29269Fixed an issue to increase log the size and the number of log files for the Cloud Services plugin.

Prisma Access 6.0.0-h9 Addressed Issues

Issue IDDescription
CYR-54776Fixed an issue where BGP filtering was enabled for all tenants in a multitenant deployment that was converted from a single tenant deployment. If you have an existing Prisma Access non-multitenant deployment and convert it to a multitenant deployment, only the first tenant (the tenant you migrated) supports BGP filtering.
CYR-53941Fixed an issue where, when onboarding remote networks using configuration import in a multi-tenant deployment, an import error was seen.
CYR-53752Fixed an issue where the Cloud Services plugin's trusted endpoint value was empty when the environment variable was set to None.
CYR-53092Fixed an issue where the Panorama commit was failing when the UI attempted to generate the IoT configuration automatically in a tenant with that had Base SITE and IOT SITE SKUs.

Prisma Access 6.0.0-h3 Addressed Issues

Issue IDDescription
CYR-53485Fixed an issue where a GlobalProtect app log certificate, which is required for ADEM, could not be generated for Prisma Access China.

Prisma Access 6.0.0 Addressed Issues

Issue IDDescription
CYR-53726Fixed an isssue where, for tenants using site-based licensing for branch sites, the site license type may display as Unknown for certain branch sites within SCMMonitorBranch Sites.
CYR-53725Fixed an issue where, for tenants using site-based licensing for branch sites, the dashboard under SCMMonitorBranch Sites might be intermittently unavailable in Prisma Access locations, including Qatar, Taiwan, Indonesia, Israel, and Saudi Arabia.
CYR-52199Fixed an issue where the drop down menu for bandwidth for Clean Pipe displayed incorrect bandwidths.
CYR-51478 Fixed an issue where, if you used Dynamic Privilege Access, using ZTNA Connectors without at least one service connection was not supported.
CYR-50707Fixed an issue where, if you were using IP Optimization with ZTNA Connector, Source IP Address stickiness (the ability for users to maintain the same egress IP for the same source IP address in a session) was not supported.
CYR-47741Fixed an issue where the Singapore Colo-Connect service connection went down after a dataplane upgrade to 10.2.10-h8.
CYR-46170Fixed an issue where, if you enabled DDNS and you later pushed a service subnet change to your mobile users, you must also restart the DDNS plugin on your Mobile User gateway for DDNS to pick up the change.
CYR-45847Fixed an issue where, when a service subnet was changed, it as updated on the Prisma Access GlobalProtect gateways, but the GlobalProtect tunnel went down because NAT was not correctly implemented.
CYR-45517Fixed an issue where, in the Colo-Connect tab, a read-only user was able to delete onboarding entries.
CYR-45341Fixed an issue where Commit and Push jobs to Colo-Connect Device Groups were timing out, causing VLANs to not be deleted.
CYR-45440Fixed an issue where, when configuring Admin Roles, the access information was not always saved correctly.
CYR-44391Fixed an issue where Explicit Proxy deployments in China did not support using the Cloud Identity Engine or SAML for authentication.
CYR-44433Fixed an issue where the status for Remote Network jobs that were successful can change from Success to Pending state.
CYR-44079Fixed an issue where the GlobalProtect DDNS logs were not rotating and the file size kept increasing.
CYR-43690Fixed an issue where, when attempting to modify or delete Connector IP Blocks in ZTNA Connector, the changes were not applied after a Commit and Push.
CYR-43062Fixed an issue where we did not support the 5.1 DDNS feature along with the IPv6 sinkhole service.
CYR-42919Fixed an issue where, when attempting to modify or delete Connector IP Blocks in ZTNA Connector, the changes are not applied after a Commit and Push.
CYR-42480Fixed an issue where private app access could be used in deployments only when Proxy Mode or Prisma Access Browser were enabled.
CYR-41838Fixed an issue where the egress IP address for Remote Networks - High Performance deployments displayed twice when you retrieved it using the Prisma Access API.
CYR-39148Fixed an issue where, when configuring Colo-Connect, Commit and Push operations to Colo Connect Device Groups might intermittently fail.
CYR-30044
Fixed an issue where predefined EDLs weren't being populated in the Block Settings list in a new Explicit Proxy deployment.