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 Access6.2.0.
The following table lists the issues addressed in Prisma Access 6.2.0.

Addressed Issues in Prisma Access 6.2

Issue ID
Description
CYR-67720Fixed 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-61110Fixed 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-29429Fixed 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.