Filter

Expand All | Collapse All

Prisma Access Docs

Release Notes
Select a Document
- 6.2 Preferred and Innovation
- 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
Activation & Onboarding
Administration
Select a Document
- 4.0 & Later
- Prisma Access China
Integrations
Incidents & Alerts

Focus

Prisma Access

Prisma Access Addressed Issues

Table of Contents

Filter

Expand All | Collapse All

Prisma Access Docs

Release Notes
Select a Document
- 6.2 Preferred and Innovation
- 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
Activation & Onboarding
Administration
Select a Document
- 4.0 & Later
- Prisma Access China
Integrations
Incidents & Alerts

Prisma Access Known Issues

Panorama Support for Prisma Access 6.2

`Prisma Access` Addressed Issues

Lists the known issues in Prisma Access6.2.0.

The following table lists the issues addressed in Prisma Access 6.2.0.

`Prisma Access` 6.2.0-h1 Addressed Issues

Issue ID	Description
CYR-70786	Fixed an issue where, in multi-tenant Panorama, plugin validation fails upon bulk import operation of the remote network configuration. The issue occurred only when the remote network had secondary WAN configuration enabled.
CYR-70444	This fix addresses commit validation error "location is invalid" when enabling IPv6 for Panorama tenants for Brazil Southeast and UK West location
CYR-69949	Fixed an issue where editing BGP Filter rules in a BGP Filter Group that is already associated to service connection nodes results in unexpected behavior in BGP Filtering functionality. Users should "un-edit" the already associated BGP Filter Group.
CYR-69289	Fixed an issue where Prisma Access Multi-tenant customer Fast Session Delete feature enablement was not taking effect upon commit push.

`Prisma Access` 6.2.0 Addressed Issues

Issue ID	Description
CYR-67720	Fixed an issue where you could not enforce Transport Layer Security (TLS) version 1.3 as the minimum TLS version for the default domain, which prevented you from utilizing the latest security protocols. With this fix, you can now configure TLSv1.3 as the minimum TLS version for the default domain.
CYR-61110	Fixed an issue where your GlobalProtect configuration status incorrectly reported as "Configuration is not in sync" after you successfully committed changes to Prisma Access. This happened when configuration metadata did not properly synchronize between Panorama and GlobalProtect as a Service (GPaaS). With this fix, your GlobalProtect configuration status accurately reflects the deployed configuration.
CYR-29429	Fixed an issue where you could not delete a Quality of Service (QoS) profile. This occurred when another subtenant used a QoS profile with the same name, even if the profile was not in use by your subtenant. With this fix, you can now delete a QoS profile regardless of whether other subtenants have identically named QoS profiles.

Prisma Access Known Issues

Panorama Support for Prisma Access 6.2