Fixed an issue where users had to create a new policy after adding an SLS license for firewalls to begin sending logs to SLS. Existing policies pushed before the license change will not send logs to SLS.

Fixed an issue where the HA cluster configuration displayed two clusters with the same name in the UI. Additionally, attempting to edit the HA pair resulted in a blank screen, preventing any modifications.

Workaround: Enable Mobile Users.

Fixed an issue where the target device count on the Schedules page displayed as zero, even though the associated rule had target devices.

Workaround: Clear the browser cache and reload the page. The target devices count should then display correctly.

Fixed an issue where PAC files larger than approximately 150 KB was failing to upload to Strata Cloud Manager, resulting in a request failed with status code 414 error.

Fixed an issue where ConfigPush was failing due to Layer 3 Aggregate Ethernet group in the imported snippet.

Fixed an issue where the performance was impacted if the number of IP pools per project exceeded 50.

Fixed an issue where the Mobile UserDDNS Configuration page didn't show the previously configured Dynamic DNS settings.

As a workaround, click on a different section and then return to the Mobile UserDDNS Configuration.

Fixed an issue where, when setting up a forwarding profile, the forwarding profile Type was displayed as ZTNA Agent instead of Prisma Access Agent. Also, if you selected Add Forwarding Profile, the drop-down displayed ZTNA Agent instead of Prisma Access Agent.

Fixed an issue where custom certificates at the device level were moved up to All container in Strata Cloud Manager. When certificates were pushed from the Strata Cloud Manager, they were also being pushed along. If you do not want to push certificates to other devices, it's advisable to move the certificates to the device level.

Added a validation to check agent configuration is not set to tunnel or hybrid mode when Enable Portal only for Proxy Mode on GlobalProtect is enabled under GlobalProtect setup.

Fixed an issue where the push with an incomplete HA pair was not working. To support HA devices in an Auto VPN cluster, both devices in the HA pair must be present together in the cluster. There is no validation in place for this and will fail the push.

Fixed an issue where you were allowed to create more than one project with the same domain and user groups if the projects were configured from different configuration snippets.

Fixed an issue where the Bandwidth Management tab displayed a blank page if the MCW configuration was present under remote networks.

Call /spiffy/v1/bp/result/policies/security_rule for a tenant.

Result: id = 3 has old check_name 'The rule Description is not populated'. The response will contain the old name. Even when new BPA analysis has been completed - the check_name remains the same.

Fixed an issue where changing the configuration was necessary to generate the new BPA report.

Fixed an issue, where pushing any Auto VPN configuration changes resulted in all admin changes being applied to all devices within the pushed VPN cluster.

Fixed an issue, wherein enabling Remote Browser Isolation (RBI) without adding any infrastructure settings and subsequently pushing the configuration changes to a remote network led to a successful push, yet the RBI configuration remained unavailable on the firewall.

Fixed an issue, where the egress IP allowlist would update automatically upon navigating to WorkflowsPrisma Access SetupGlobalProtectPrisma Access Locations page.

Fixed an issue where the configured GlobalProtect IPSec Crypto profile couldn’t be deleted or cloned since the WorkflowsPrisma Access SetupGlobalProtectGlobalProtect AppGlobal App Settings page did not show the configured GlobalProtect IPSec Crypto profiles.

Fixed an issue where the IP Restrictions weren’t accurately enforced when configured with an IP address range.