Prisma Access Addressed Issues
Focus
Focus
Prisma Access

Prisma Access Addressed Issues

Table of Contents

Prisma Access Addressed Issues

Lists the known issues in Prisma Access 6.1.0.
The following table lists the issues addressed in Prisma Access 6.1.0.
Issue ID
Description
CYR-58852
Fixed an issue where Panorama commit validation workflows would fail if a tenant's licenses had the "no_limit" string under the service_connection local service chain information in the license_capabilities. This occurred because the system was attempting to convert the string to an integer.
CYR-58332
Fixed an issue where commits to GlobalProtect gateways failed with a validation error related to the `max-version` setting in the SSL-TLS service profile.
CYR-58134
Fixed an issue where upgrading the cloud_services plugin from version 5.1.0-39 to 6.0.0-11 on Panorama automatically disabled the "Enable Private App Access" option. When this configuration was pushed to Prisma Access, it caused an outage to critical internal applications.
CYR-57700
Fixed an issue where any changes to the Cloud Services Plugin onboarding configuration on Panorama resulted in an error when the 'DEFAULT' config was missing in the GlobalProtect portal.
CYR-57636
Fixed an issue where Panorama could not display bandwidth usage statistics for remote networks in the tenant status view when managing Prisma Access with multitenancy enabled.
CYR-55432
Fixed an issue where Internal Host Detection (IHD) details were grayed out during Mobile User onboarding.
CYR-54503
Fixed an issue where domain configurations were not applied to mobile users during a partial commit on Panorama, while the same configurations were successfully applied to remote networks.
CYR-53941
Fixed an issue where, when onboarding remote networks using configuration import in a multitenant deployment, an import error was seen.
CYR-51619
Fixed an issue where, after creating a new regional IP pool for IP the pool group 31 region, a 'blank ip pool' message was received in the Cloud services plugin UI.
CYR-49944
Fixed an issue where a secondary DNS server was configured, which is not allowed.