Prisma Access
Prisma Access Addressed Issues
Table of Contents
Expand All
|
Collapse All
Prisma Access Docs
-
- 6.1 Preferred and Innovation
- 6.0 Preferred and Innovation
- 5.2 Preferred and Innovation
- 5.1 Preferred and Innovation
- 5.0 Preferred and Innovation
- 4.2 Preferred
- 4.1 Preferred
- 4.0 Preferred
- 3.2 Preferred and Innovation
- 3.1 Preferred and Innovation
- 3.0 Preferred and Innovation
- 2.2 Preferred
-
-
- 4.0 & Later
- Prisma Access China
-
-
Prisma Access Addressed Issues
Lists the known issues in Prisma Access6.1.0.
The following table lists the issues addressed in Prisma Access 6.1.0.
Addressed Issues in Prisma Access 6.1.0-h2
|
Issue ID
|
Description
|
|---|---|
| CYR-62135 | Fixed an issue where, in a multitenant Panorama managed Prisma Access deployment, internal host detection could not be configured by device group and template admin users. |
| CYR-61659 | Fixed an issue where, before changing the infrastructure subnet, administrators were not provided a message indicating that a maintenance window and a TAC case is required. |
| CYR-61474 | Fixed an issue where the Explicit Proxy feature in Prisma Access displayed "Prisma Access Browser" instead of "Prisma Browser". |
| CYR-61443 | Fixed an issue where, under the OnboardingService Connection area in Strata Cloud Manager, when Colo-Connect service connections are onboarded, the BGP-specific column that includes overlay BGP status and peer RIB and routing table information displayed a pop-up window with an error that the BGP status couldn't be found. |
| CYR-60959 | Fixed an issue where, when enabling Private Application Access in Explicit Proxy and ZTNA Connector is also configured, an error message displayed that there was not a service connection deployed. |
| CYR-59412 | Fixed an issue where serviceability commands did not yield any output in a tenant that had Dynamic Privilege Access enabled. |
| CYR-54776 | Fixed an issue where BGP filtering was enabled on a Panorama in a multi-tenant deployment that had no supertenant. BGP filtering is not supported on a Panorama in a multi-tenant deployment that has no supertenant. |
| CYR-52444 | Fixed an issue where, in a multitenant Panorama Managed Prisma Access deployment, the BGP Filtering feature was supported only on a parent Tenant and was not supported on sub-tenants. |
Addressed Issues in Prisma Access 6.1.0-h1
|
Issue ID
|
Description
|
|---|---|
| CYR-61065 | Fixed an issue where a Panorama local commit failed with a validation error: Failed Plugin Validation error after a Cloud Services Plugin upgrade. |
| CYR-60869 | Fixed an issue where the export operation failed to download the Remote Network configuration from Panorama. |
| CYR-60105 | Fixed an issue where the Panorama one-time password (OTP) workflow for a new deployment failed from the UI. |
| CYR-59494 | Fixed an issue where the list of Remote Networks on the Remote Networks status page displayed a count of 0. |
| CYR-58530 | Fixed an issue on Panorama where you could not update hypervisor profile fields when an on-premises deployment was pending. |
| CYR-55824 | Fixed an issue where the Panorama UI did not allow BGP configuration for the passive tunnel in an Active/Passive tunnel configuration. |
| CYR-54007 | Fixed an issue where, after reducing the Remote Network's aggregate bandwidth from a Safari browser, the browser fails to display the list of unused SPN names that will be released. |
Addressed Issues 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.
|