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.

Prisma Access 6.2.0 Addressed Issues

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.

Prisma Access 6.2.0-h2 Addressed Issues

Issue ID
Description
CYR-70945Fixed an issue where plugin validation fails on Panorama MT/MU because the adem-aiops-users value is set to 400, which falls below the minimum required value per tenant (0).
CYR-70755Fixed an issue where the CIE profile is not added under device group for explicit proxy in Panorama.
CYR-67131Fixed an issue where the Panorama UI mistakenly includes "Service Connection" in the Licenses and Status tabs for Business Premium licenses, which lack Service Connection support.
CYR-66457
Fixed an issue so that during MU onboarding, the Internal Host Detection value is now strictly mapped to the DEFAULT Agent Settings profile in the portal.
  • Strict Mapping: The Internal Host Detection value will only copy to the DEFAULT named Agent Settings profile. It will no longer automatically fall back to the first or top-most Agent Settings profile if DEFAULT is absent.
  • No Profile Fallback: If a DEFAULT Agent Settings profile does not exist in the portal, the Internal Host Detection value will not be applied to any alternative Agent Settings profiles.
  • Admin Control: Administrators retain full flexibility to manually update or modify the Internal Host Detection value directly within the DEFAULT portal Agent Settings at any time.

Prisma Access 6.2.0-h1 Addressed Issues

Issue ID
Description
CYR-70786Fixed 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-70444This fix addresses commit validation error "location is invalid" when enabling IPv6 for Panorama tenants for Brazil Southeast and UK West location
CYR-69949Fixed 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-69289Fixed an issue where Prisma Access Multi-tenant customer Fast Session Delete feature enablement was not taking effect upon commit push.