Prisma Access Addressed Issues
Table of Contents
Expand All
|
Collapse All
Prisma Access Docs
-
3.2 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
-
- Features in Prisma Access 3.2 and 3.2.1
- Changes to Default Behavior
- Upgrade the Cloud Services Plugin
- Prisma Access Known Issues
- Prisma Access Addressed Issues
- Release Updates for Reports
-
- Features in Prisma Access 3.1 Preferred and Innovation
- Features in Prisma Access 3.0 Preferred and Innovation
- Features Introduced in Prisma Access 2.2 Preferred
- Features Introduced in Prisma Access 2.1 Innovation
- Features Introduced in Prisma Access 2.1 Preferred
- Features Introduced in Prisma Access 2.0 Innovation
- Features Introduced in Prisma Access 2.0 Preferred
- Features Introduced in Prisma Access 1.8
- Features Introduced in Prisma Access 1.7
- Features Introduced in Prisma Access 1.6.1
- Features Introduced in Prisma Access 1.6.0
- Features Introduced in Prisma Access 1.5.1
- Features Introduced in Prisma Access 1.5.0
- Features Introduced in Prisma Access 1.4.0
- Features Introduced in Prisma Access 1.3.1
- Features Introduced in Prisma Access 1.3.0
- Features Introduced in Prisma Access 1.2.0
- Features Introduced in Prisma Access 1.1.0
- Getting Help
-
-
-
-
- Allocate Licenses for Prisma Access (Managed by Strata Cloud Manager)
- Plan Service Connections for Prisma Access (Managed by Strata Cloud Manager) and Add-ons
- Add Additional Locations for Prisma Access (Managed by Strata Cloud Manager) and Add-ons
- Enable Available Add-ons for Prisma Access (Managed by Strata Cloud Manager)
- Search for Subscription Details
- Share a License for Prisma Access (Managed by Strata Cloud Manager) and Add-ons
- Increase Subscription Allocation Quantity
-
- Activate a License for Prisma Access (Managed by Strata Cloud Manager) and Prisma SD-WAN Bundle
- Activate and Edit a License for SASE 5G Through Common Services
-
- Prisma Access Onboarding Workflow
-
4.0 & Later
- 4.0 & Later
- 3.2 Preferred and Innovation
- 3.1 Preferred and Innovation
- 3.0 Preferred and Innovation
- 2.2 Preferred
- Prisma Access China
-
- Set Up Prisma Access
- Configure the Prisma Access Service Infrastructure
- Remote Networks: IPSec Termination Nodes and Service IP Addresses
- Remote Networks: IP Address Changes Related To Bandwidth Allocation
- Remote Networks: Service IP Address and Egress IP Address Allocation
- API Examples for Retrieving Prisma Access IP Addresses
- Get Notifications When Prisma Access IP Addresses Change
- Prisma Access Zones
- DNS for Prisma Access
- High Availability for Prisma Access
-
- Enable ZTNA Connector
- Delete Connector IP Blocks
- Set Up Auto Discovery of Applications Using Cloud Identity Engine
- Private AWS Application Target Discovery
- Security Policy for Apps Enabled with ZTNA Connector
- Monitor ZTNA Connector
- View ZTNA Connector Logs
- Preserve User-ID Mapping for ZTNA Connector Connections with Source NAT
-
- Enable Dynamic Privilege Access for Prisma Access Through Common Services
- Authorize User Group Mapping in Cloud Identity Engine for Dynamic Privilege Access
- Enable the Access Agent
- Set Up the Agent Infrastructure for Dynamic Privilege Access
- Create a Snippet
- Create a Project
- Traffic Steering for Dynamic Privilege Access
- Push the Prisma Access Agent Configuration
- Download the Dynamic Privilege Access Enabled Prisma Access Agent Package
-
- Install the Prisma Access Agent
- Log in to the Dynamic Privilege Access Enabled Prisma Access Agent
- Change Preferences for the Dynamic Privilege Access Enabled Prisma Access Agent
- Connect the Dynamic Privilege Access Enabled Prisma Access Agent to a Different Location
- Switch to a Different Project
- Connect the Dynamic Privilege Access Enabled Prisma Access Agent to a Different Server
- Disable the Dynamic Privilege Access Enabled Prisma Access Agent
- Switch Between the Prisma Access Agent and GlobalProtect App
- View and Monitor Dynamic Privilege Access Users
- View and Monitor Dynamic Privilege Access Projects
- Automatic Tunnel Restoration in Dynamic Privilege Access Prisma Access Agents
- Manage Prisma SASE 5G
- App Acceleration in Prisma Access
-
-
- Planning Checklist for GlobalProtect on Prisma Access
- Set Up GlobalProtect Mobile Users
- GlobalProtect — Customize Tunnel Settings
- GlobalProtect — Customize App Settings
- Ticket Request to Disable GlobalProtect
- GlobalProtect Pre-Logon
- GlobalProtect — Clientless VPN
- Monitor GlobalProtect Mobile Users
- How the GlobalProtect App Selects Prisma Access Locations for Mobile Users
- Allow Listing GlobalProtect Mobile Users
-
- Explicit Proxy Configuration Guidelines
- GlobalProtect in Proxy Mode
- GlobalProtect in Tunnel and Proxy Mode
- Private IP Address Visibility and Enforcement for Agent Based Proxy Traffic
- SAML Authentication for Explicit Proxy
- Set Up Explicit Proxy
- Cloud Identity Engine Authentication for Explicit Proxy Deployments
- Proxy Mode on Remote Networks
- How Explicit Proxy Identifies Users
- Explicit Proxy Forwarding Profiles
- PAC File Guidelines
- Explicit Proxy Best Practices
- Monitor and Troubleshoot Explicit Proxy
- Block Settings for Explicit Proxy
- Use Special Objects to Restrict Explicit Proxy Internet Traffic to Specific IP Addresses
- Access Your Data Center Using Explicit Proxy
- App-Based Office 365 Integration with Explicit Proxy
- Chromebook with Prisma Access Explicit Proxy
- Configure Proxy Chaining with Blue Coat Proxy
- Configure Proxy Chaining on Prisma Access Explicit Proxy
- IP Address Optimization for Explicit Proxy Users- Proxy Deployments
- DNS Resolution for Mobile Users—Explicit Proxy Deployments
- View User to IP Address or User Groups Mappings
- Report Mobile User Site Access Issues
- Enable Mobile Users to Access Corporate Resources
-
-
- Planning Checklist for Remote Networks
- Allocate Remote Network Bandwidth
- Onboard a Remote Network
- Connect a Remote Network Site to Prisma Access
- Enable Routing for Your Remote Network
- Onboard Multiple Remote Networks
- Configure Remote Network and Service Connection Connected with a WAN Link
- Remote Networks—High Performance
- Integrate a Shared Desktop VDI with Prisma Access Using Terminal Server
-
- Multitenancy Configuration Overview
- Plan Your Multitenant Deployment
- Create an All-New Multitenant Deployment
- Enable Multitenancy and Migrate the First Tenant
- Add Tenants to Prisma Access
- Delete a Tenant
- Create a Tenant-Level Administrative User
- Sort Logs by Device Group ID in a Multitenant Deployment
-
- Add a New Compute Location for a Deployed Prisma Access Location
- How BGP Advertises Mobile User IP Address Pools for Service Connections and Remote Network Connections
- Proxy Support for Prisma Access and Strata Logging Service
- Block Incoming Connections from Specific Countries
- Prisma Access for No Default Route Networks
-
-
- Default Routes With Prisma Access Traffic Steering
- Traffic Steering in Prisma Access
- Traffic Steering Requirements
- Default Routes with Traffic Steering Example
- Default Routes with Traffic Steering Direct to Internet Example
- Default Routes with Traffic Steering and Dedicated Service Connection Example
- Prisma Access Traffic Steering Rule Guidelines
- Configure Zone Mapping and Security Policies for Traffic Steering Dedicated Connections
- Configure Traffic Steering in Prisma Access
- Preserve User-ID and Device-ID Mapping for Service Connections with Source NAT
-
- Prisma Access Internal Gateway
-
- Configure Privileged Remote Access Settings
- Set Up the Privileged Remote Access Portal
- Configure Applications for Privileged Remote Access
- Set Up Privileged Remote Access Profiles
- Define Permissions for Accessing Privileged Remote Access Apps
- Configure Split Tunneling for Privileged Remote Access Traffic
- Manage Privileged Remote Access Connections
- Use Privileged Remote Access
-
- Integrate Prisma Access With Other Palo Alto Networks Apps
- Integrate Third-Party Enterprise Browser with Explicit Proxy
- Integrate Third-Party NDRs with Prisma Access
- Juniper Mist Integration for SASE Health
-
-
- Connect your Mobile Users in Mainland China to Prisma Access Overview
- Configure Prisma Access for Mobile Users in China
- Configure Real-Name Registration and Create the VPCs in Alibaba Cloud
- Attach the CEN and Specify the Bandwidth
- Create Linux Instances in the Alibaba Cloud VPCs
- Configure the Router Instances
- Onboard the GlobalProtect Gateway and Configure the Prisma Access Portal
-
-
-
- INC_MU_APP_EXPERIENCE_UNREACHABLE_ ALL_PA_LOCATIONS
- INC_MU_APP_EXPERIENCE_UNREACHABLE_ PER_PA_LOCATION
- INC_RN_APP_EXPERIENCE_UNREACHABLE_ ALL_PA_LOCATIONS
- INC_RN_APP_EXPERIENCE_UNREACHABLE_ ONE_PA_LOCATION
- INC_CIE_AGENT_DISCONNECT
- INC_CIE_DIRECTORY_DISCONNECT
- INC_GLOBALPROTECT_GW_USER_AUTH_ TIMEOUT_FAILURES_COUNT_EXCEEDED_ ABOVE_BASELINE_ALL_PA_LOCATIONS
- INC_GLOBALPROTECT_GW_USER_AUTH_ TIMEOUT_FAILURES_COUNT_EXCEEDED_ ABOVE_BASELINE_PER_PA_LOCATION
- INC_GLOBALPROTECT_PORTAL_AUTH_ TIMEOUT_FAILURES_COUNT_EXCEEDED_ ABOVE_BASELINE_ALL_PA_LOCATIONS
- INC_GLOBALPROTECT_PORTAL_AUTH_ TIMEOUT_FAILURES_COUNT_EXCEEDED_ ABOVE_BASELINE_PER_PA_LOCATION
- INC_MU_AUTH_SERVER_UNREACHABLE_ALL_ PA_LOCATIONS
- INC_MU_AUTH_SERVER_UNREACHABLE_PER_ PA_LOCATION
- INC_MU_DNS_SERVER_UNREACHABLE_ALL_ PA_LOCATIONS
- INC_MU_DNS_SERVER_UNREACHABLE_ PER_PA_LOCATION
- INC_PORTAL_CLIENTLESS_VPN_AUTH_ TIMEOUT_FAILURES_COUNT_EXCEEDED_ ABOVE_BASELINE_ALL_PA_LOCATIONS
- INC_PORTAL_CLIENTLESS_VPN_AUTH_ TIMEOUT_FAILURES_COUNT_EXCEEDED_ ABOVE_BASELINE_PER_PA_LOCATION
- INC_RN_AUTH_SERVER_UNREACHABLE_ALL_ PA_LOCATIONS
- INC_RN_AUTH_SERVER_UNREACHABLE_PER_ PA_LOCATION
- INC_RN_DNS_SERVER_UNREACHABLE_ALL_ PA_LOCATIONS
- INC_RN_DNS_SERVER_UNREACHABLE_PER_ PA_LOCATION
- INC_RN_ECMP_TUNNEL_RTT_EXCEEDED_ BASELINE
- INC_RN_PRIMARY_WAN_TUNNEL_RTT_ EXCEEDED_BASELINE
- INC_RN_SECONDARY_TUNNEL_DOWN
- INC_RN_SECONDARY_WAN_TUNNEL_RTT_ EXCEEDED_BASELINE
- INC_RN_SITE_CAPACITY_PREDICTION
- INC_SC_PRIMARY_WAN_TUNNEL_RTT_ EXCEEDED_BASELINE
- INC_SC_SECONDARY_WAN_TUNNEL_RTT_ EXCEEDED_BASELINE
- INC_SC_SITE_CAPACITY_PREDICTION
-
- INC_CERTIFICATE_EXPIRY
- INC_GP_CLIENT_VERSION_UNSUPPORTED
- INC_MU_IP_POOL_BLOCK_UTILIZATION_ EXCEEDED_CAPACITY
- INC_MU_IP_POOL_BLOCK_UTILIZATION_ EXCEEDED_THRESHOLD
- INC_PA_INFRA_DEGRADATION
- INC_PA_SERVICE_DEGRADATION_PA_LOCATION
- INC_PA_SERVICE_DEGRADATION_RN_ SITE_CONNECTIVITY
- INC_PA_SERVICE_DEGRADATION_SC_ CONNECTIVITY
- INC_RN_ECMP_BGP_DOWN
- INC_RN_ECMP_BGP_FLAP
- INC_RN_ECMP_PROXY_TUNNEL_DOWN
- INC_RN_ECMP_PROXY_TUNNEL_FLAP
- INC_RN_ECMP_TUNNEL_DOWN
- INC_RN_ECMP_TUNNEL_FLAP
- INC_RN_PRIMARY_WAN_BGP_FLAP
- INC_RN_PRIMARY_WAN_PROXY_TUNNEL_DOWN
- INC_RN_PRIMARY_WAN_PROXY_TUNNEL_FLAP
- INC_RN_PRIMARY_WAN_TUNNEL_DOWN
- INC_RN_PRIMARY_WAN_TUNNEL_FLAP
- INC_RN_SECONDARY_WAN_BGP_DOWN
- INC_RN_SECONDARY_WAN_BGP_FLAP
- INC_RN_SECONDARY_WAN_PROXY_TUNNEL_DOWN
- INC_RN_SECONDARY_WAN_PROXY_TUNNEL_FLAP
- INC_RN_SECONDARY_WAN_TUNNEL_DOWN
- INC_RN_SECONDARY_WAN_TUNNEL_FLAP
- INC_RN_SITE_DOWN
- INC_RN_SITE_LONG_DURATION_CAPACITY_ EXCEEDED_THRESHOLD
- INC_RN_SITE_LONG_DURATION_EXCEEDED_ CAPACITY
- INC_RN_SPN_LONG_DURATION_CAPACITY_EXCEEDED _THRESHOLD
- INC_RN_SPN_LONG_DURATION_EXCEEDED_ CAPACITY
- INC_SC_PRIMARY_WAN_BGP_DOWN
- INC_SC_PRIMARY_WAN_BGP_FLAP
- INC_SC_PRIMARY_WAN_PROXY_TUNNEL_DOWN
- INC_SC_PRIMARY_WAN_PROXY_TUNNEL_FLAP
- INC_SC_PRIMARY_WAN_TUNNEL_DOWN
- INC_SC_PRIMARY_WAN_TUNNEL_FLAP
- INC_SC_SECONDARY_WAN_BGP_DOWN
- INC_SC_SECONDARY_WAN_BGP_FLAP
- INC_SC_SECONDARY_WAN_PROXY_TUNNEL_DOWN
- INC_SC_SECONDARY_WAN_PROXY_TUNNEL_FLAP
- INC_SC_SECONDARY_WAN_TUNNEL_DOWN
- INC_SC_SECONDARY_WAN_TUNNEL_FLAP
- INC_SC_SITE_DOWN
- INC_SC_SITE_LONG_DURATION_CAPACITY_ EXCEEDED_THRESHOLD
- INC_SC_SITE_LONG_DURATION_EXCEEDED_ CAPACITY
- INC_ZTNA_CONNECTOR_APP_STATUS_DOWN
- INC_ZTNA_CONNECTOR_APP_STATUS_DOWN_PARTIAL
- INC_ZTNA_CONNECTOR_CPU_HIGH
- INC_ZTNA_CONNECTOR_MEMORY_HIGH
- INC_ZTNA_CONNECTOR_TUNNEL_DOWN
-
- AL_CIE_AGENT_DISCONNECT
- AL_CIE_DIRECTORY_DISCONNECT
- AL_MU_IP_POOL_CAPACITY
- AL_MU_IP_POOL_USAGE
- AL_RN_ECMP_BGP_DOWN
- AL_RN_ECMP_BGP_FLAP
- AL_RN_PRIMARY_WAN_BGP_DOWN
- AL_RN_PRIMARY_WAN_BGP_FLAP
- AL_RN_PRIMARY_WAN_TUNNEL_DOWN
- AL_RN_PRIMARY_WAN_TUNNEL_FLAP
- AL_RN_SECONDARY_WAN_BGP_DOWN
- AL_RN_SECONDARY_WAN_BGP_FLAP
- AL_RN_SECONDARY_WAN_TUNNEL_DOWN
- AL_RN_SECONDARY_WAN_TUNNEL_FLAP
- AL_RN_SITE_DOWN
- AL_RN_SITE_LONG_DURATION_CAPACITY_ EXCEEDED_THRESHOLD
- AL_RN_SITE_LONG_DURATION_EXCEEDED_ CAPACITY
- AL_RN_SPN_LONG_DURATION_CAPACITY_ EXCEEDED_THRESHOLD
- AL_SC_PRIMARY_WAN_BGP_DOWN
- AL_SC_PRIMARY_WAN_BGP_FLAP
- AL_SC_PRIMARY_WAN_TUNNEL_DOWN
- AL_SC_PRIMARY_WAN_TUNNEL_FLAP
- AL_SC_SECONDARY_WAN_BGP_DOWN
- AL_SC_SECONDARY_WAN_BGP_FLAP
- AL_SC_SECONDARY_WAN_TUNNEL_DOWN
- AL_SC_SECONDARY_WAN_TUNNEL_FLAP
- AL_SC_SITE_DOWN
- AL_SC_SITE_LONG_DURATION_CAPACITY_ EXCEEDED_THRESHOLD
- AL_SC_SITE_LONG_DURATION_EXCEEDED_CAPACITY
- AL_ZTNA_CONNECTOR_APP_STATUS_DOWN
- AL_ZTNA_CONNECTOR_APP_STATUS_DOWN_PARTIAL
- AL_ZTNA_CONNECTOR_CPU_HIGH
- AL_ZTNA_CONNECTOR_MEMORY_HIGH
- AL_ZTNA_CONNECTOR_TUNNEL_DOWN
- New Features in Incidents and Alerts
- Known Issues
Prisma Access Addressed Issues
The following topics describe issues
that have been addressed in Prisma Access:
Prisma Access 3.2.1-h98 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-43237 | Fixed an issue where Panorama Managed Prisma Access deployments that use proxies did not work with Prisma SD-WAN deployments using Prisma Access CloudBlade Integration Release 4.0.0. |
| CYR-42499 | Fixed an issue where, in a new multitenant deployment that didn't have any existing configuration, administrators were not allowed to enter the sub-tenant name manually. |
| CYR-41857 | Fixed an issue where if the user did not configure QoS profiles under NetworksQoS Profile, the local commit validation on Panorama plugin was getting skipped. |
| CYR-41569 | Fixed an issue where, when only one region was onboarded in a Mobile Users—GlobalProtect deployment, removing a location in that region resulted in a plugin validation error. |
| CYR-41472 | Fixed an issue in a multitenant environment where, if users did not provide units for Remote Networks or Mobile User in the sub-tenant creation tab, the error message displayed Please specify a bandwidth for your Clean Pipe deployment instead of Please specify a bandwidth for your Remote Networks/Mobile Users. |
| CYR-39874 | Fixed an issue where an Explicit Proxy template was created without Explicit Proxy being onboarded, which caused an issue when Explicit Proxy was onboarded later. |
Prisma Access 3.2.1-h94 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-41084 | Fixed an issue where, after disabling the Cloud Identity Engine integration with Prisma Access, existing Group Mapping Settings caused an error upon commit. |
| CYR-38605 | Fixed an issue where the rebranded Strata Logging Service name of Strata Logging Service was not displaying correctly. |
| CYR-29408 | Fixed an issue where the Cloud Services plugin did not manage SDWAN devices that were deployed in Fedramp environments. |
Prisma Access 3.2.1-h91 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-34770 | Fixed an issue where, if you configured multiple portals in Prisma Access for the Mobile Users - GlobalProtect deployment, you must also configure an authentication profile under Client Authentication on all portals. |
| CYR-39795 | Fixed an issue where, after installation of the Cloud Services plugin, an Explicit Proxy Kerberos server profile (default_server_profile) was installed by the __cloud_services user, even though Explicit Proxy was not enabled. |
Prisma Access 3.2.1-h89 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-37665 | Fixed an issue where, after migrating a tenant to a multi-tenant deployment, the Explicit_Proxy_Template was not created correctly and commit failed for the first tenant that was migrated. |
| CYR-37244 | Fixed an issue where, after upgrading the Panorama that manages Prisma Access to a PAN-OS version of 11.0.0 or later, the Delete button in the Remote Networks onboarding section was not enabled when a Remote Network was selected. |
| CYR-36895 | Fixed an issue where the IPv6 proxy-ID tab was missing when IPv6 was enabled for multi-tenant setups. |
| CYR-34482 | Fixed an issue where two Data Filtering tabs are seen under the Objects tab and one tab is undefined. |
| CYR-24798 | Fixed an issue where, in multi-tenant mode, there is no space between the Unallocated text and the unallocated bandwidth number in the multi-tenant bandwidth allocation window. |
| CYR-22671 | Fixed an issue where, in a multi-tenant deployment, the first tenant (the tenant you migrated) had prefixes appended to the device groups, templates, and template stacks such ar mu-dg, rn-tpl, and so forth. Only the tenants you create after you migrate the first tenant should have prefixes appended. |
Prisma Access 3.2.1-h83 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-35838 | Fixed an issue where sub-tenants were being inadvertently deprovisioned during a Panorama commit. This fix includes a plugin enhancement where subtenants will need to be explicitly deprovisioned by the Panorama admin to remove them from the Prisma Access infrastructure. |
| CYR-30610 | Fixed an issue where, in a Prisma Access multitenant deployment, Commit and Push operations were failing because subtenant IDs were not being populated correctly. |
Prisma Access 3.2.1-h78 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-36213 | Fixed an issue where an internal daemon was restarting, which caused a configuration sync status issue on Panorama. |
|
CYR-35811
|
Fixed an issue where a Commit and Push
operation was failing due to an empty subtenant ID for a newly
added subtenant.
|
| CYR-34966 | Fixed an issue where, when assigning Customize Per Site values for QoS for remote networks, remapped locations could not be selected or customized. |
Prisma Access 3.2.1-h74 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-37003 |
Fixed an issue where, after upgrading the Panorama that manages
Prisma Access to 10.2, multitenant deployments had one or more
sub-tenants deleted after a local commit was performed. Note
that, after you install the plugin that contains this hotfix and
delete a tenant, the tenant is deleted locally on the Panorama
but its configuration remains in the Prisma Access
infrastructure.
It is recommended that you backup your Panorama configuration
before you delete any sub-tenants.
To completely delete the tenant, reach out to your Palo Alto
Networks account representative or partner, who will contact the
SRE team and submit a request to delete the tenant from your
infrastructure.
|
Prisma Access 3.2.1-h70 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-33526 | Fixed an issue where Prisma Access attempted to fetch user attributes from Cloud Identity Engine (CIE) on every commit and push instead of just when the Directory Sync Service Group Mapping Settings configuration changed. |
| CYR-33761 | Fixed an issue where, when after clicking Integrate with SDWAN under Cloud Services Configuration, the button is not hidden even though the integration completed successfully. |
Prisma Access 3.2.1-h68 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-35078 | Fixed an issue where an internal DNS domain could not be set and the following message was displayed: Invalid wildcard domain name. The domain name can have only one asterisk in the first position. |
| CYR-34966 | Fixed an issue where remapped compute locations did not display in the QoS settings for remote networks under Customize Per Site. |
| CYR-34616 | Fixed an issue where the PanoramaQoS Statistics page displayed an inflated number of dropped packets. |
| CYR-34456 | Fixed an issue where, when Prisma Access created a new compute location and remapped an existing remote network location to that new location, if you did not delete and re-add the existing compute location to take advantage of the latest compute location-to-location mapping, you could not view bandwidth statistics for the remapped location. |
| CYR-34053 | Fixed an issue where, after a compute location was remapped, remote network QoS settings could not be applied to the remapped compute location. |
| CYR-21629 | Fixed an issue where, when Prisma Access created a new compute location and remapped an existing remote network location to that new location, if you did not delete and re-add the existing compute location to take advantage of the latest compute location-to-location mapping, you cloud not view bandwidth statistics for the remapped location. |
Prisma Access 3.2.1-h63 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-34429 | Fixed an issue where local commits were failing after an upgrade to the 4.1.0 Cloud Services plugin. |
| CYR-34118 | Fixed an issue where, if using Explicit Proxy in multitenant mode and after upgrading to 3.2.0+ plugin, Block Settings and Authentication Settings migrations did not take place. |
| CYR-33969 | Fixed an issue where a Mobile Users - GlobalProtect configuration was deleted without the plugin user having deleted the configuration. |
| CYR-33805 | Fixed an issue where the Remote Networks and Mobile Users text in the Multi Tenant creation window was misaligned and did not properly indicate which component the allocation charts were for. |
| CYR-25509 | Fixed an issue where an unsupported debug command was exposed. |
Prisma Access 3.2.1-h58 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-33844 | Fixed an issue where the following Cloud Services
plugin builds were not compatible with the following M-series
Panorama devices:
|
| CYR-33757 | Fixed an issue in the Traffic Steering Rule Source tab where clicking on a Source Address or Address-Group in the drop-down list caused an incorrect item in the list to be selected. |
| CYR-33695 | Fixed an issue where traffic steering rules could not be disabled or moved, and in other cases, a No object to edit in move handler error was encountered and no changes could be applied to the traffic steering rule. |
| CYR-32221 | Fixed an issue where, after clicking on the Connection Name of a Remote Network and then returning back to the previous page, the Peer IP Address displayed as Loading. |
| CYR-32186 | Fixed an issue where a Permission Denied error was received when attempting to delete a remote network. |
Prisma Access 3.2.1-h48 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-27018 | Fixed an issue where the Cloud Services Plugin was not able to send dynamic updates requests using nsupdate to the external DNS server. |
Prisma Access 3.2.1-h41 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-31832 | Fixed an issue where changing remote network or mobile user configurations were taking a long time to complete after clicking OK. |
| CYR-31541 | Fixed an issue where, when enabling Multi-Tenancy, an error occurred if the tenant name was longer than 24 characters. |
| CYR-31173 | Fixed an issue where when exporting CSV data for all active mobile users, data for only 9000 users was exported instead of for all users. |
| CYR-29945 | Fixed an issue where Clientless VPN was getting enabled every time the cloud configuration was updated, causing the commit to fail. |
| CYR-23502 | Fixed an issue where, when downloading current mobile user information from locations in the Japan Central compute location, the downloaded CSV information differed from the results obtained in the UI. |
Prisma Access 3.2.1-h36 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-31236 | Fixed an issue where the SSH Management Profiles Settings tab was missing from templates. |
| CYR-31103 | Fixed an issue where when creating a new subnet with a new access domain, duplicate templates were created under the access domain. |
| CYR-30770 | Fixed an issue where, in a multi-tenant setup when sub-tenants were changed under StatusNetwork DetailsRemote Networks, the Local IP address was not correctly showing the IP address. |
| CYR-29431 |
Fixed an issue where modifying the Mobile User GlobalProtect
gateway configuration to use a SAML IdP authentication profile
and clicking okay caused an extra configuration to be added to
Panorama, which also caused commit to fail with an error
interface '-' is not a valid
reference'.
|
| CYR-29160 | Fixed an issue where the GlobalProtect App Log certificate was not getting saved when Panorama was in FIPS-CC mode. |
| CYR-27018 | Fixed an issue where the gp_ddns_support.log file was missing, preventing use of the DDNS feature to resolve computer names to user IP mapping associations. |
Prisma Access 3.2.1-h30 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-30428 |
Fixed an issue where, in the event of the creation of a
subtenant, modification of bandwidth allocated to existing
subtenants no longer worked as expected.
|
| CYR-30332 |
Fixed an issue where, if you have configured inbound access, the
Peer IP Address did not display in
the PanoramaCloud ServicesConfigurationInbound Access Remote Networks tab.
|
| CYR-30319 |
Fixed an issue where the secret key generation for a Prisma
SD-WAN integration with Prisma Access failed.
|
| CYR-30072 |
Fixed an issue where custom device groups that were a parent of
the Explicit Proxy Device Group could not use predefined special
objects without causing a commit error.
|
| CYR-29464 |
Fixed an issue where the Peer IP Address
did not display in a multitenant deployment.
|
| CYR-23943 |
Fixed an issue where, in a Panorama Managed multitenant
deployment, the first tenant had a different name in Insights
than in Panorama.
|
Prisma Access 3.2.1-h21 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-30208 |
Fixed an issue where a commit on a new Panorama appliance with
Explicit Proxy configuration failed with a
missing
users error.
|
| CYR-29891 |
Fixed an issue where, when users access the GlobalProtect Portal
without accessing the Cloud Services plugin, the portal agent
config might not be synchronized.
|
| CYR-29809 |
Fixed an issue where, if the user onboarded mobile users
locations and did not choose any locations to be selected under
Manual Gateway Locations tab, subsequent local commits on the
Panorama appliance was failing with the error
Failed to find any locations in
path:
cloud_services/mobile-users/onboarding/entry/manual-gateway/region/entry/locations/member
regions validation for manual-gateway failed for
Mobile Users. Failed plugin
validation.
|
Prisma Access 3.2.1-h12 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-29598 |
Fixed an issue where, after upgrading the Panorama version to
10.2.3, a local commit to Panorama took a long amount of time
(10 to 15 minutes).
|
| CYR-29495 |
Fixed an issue where, when adding a new agent configuration, the
GlobalProtect portal and gateway show the Generate
cookie for authentication override and
Accept cookie for authentication
override choices disabled in the UI.
|
| CYR-29185 |
Fixed an issue where Administrative users who use role-based
access control (RBAC) were not assigned the correct RBAC
privileges after a Cloud Services plugin upgrade.
|
| CYR-28926 |
Fixed an issue where Admin Role Profiles did not have the correct
administrative privileges.
|
| CYR-26516 |
Fixed an issue where, when the IP Allowlist feature has
Using IP Allow List in SaaS Apps set
to Yes, the Egress IP Allowlist table was
not populated without refreshing the page.
|
| CYR-23943 |
Fixed an issue where, in a Panorama Managed multitenant
deployment, the first tenant had a different name in Insights
than in Panorama.
|
Prisma Access 3.2.1-h5 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-28830 |
Fixed an issue where device identification was not being enabled
on the zones.
|
| CYR-28781 |
Fixed an issue where there was no online help for the
On-Prem Proxy tab in the Cloud
Services plugin UI.
|
| CYR-22276 |
Fixed an issue where, in the Egress IP Allowlist table,
newly-added IP addresses were marked as Undefined.
|
Prisma Access 3.2.1 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-34482 | Fixed an issue where two Data Filtering tabs are seen under Objects tab and one tab is undefined. |
| CYR-28180 |
Fixed an issue where, when multiple portals were configured in a
Mobile Users—GlobalProtect deployment, configuration details
were not synchronized for the portal using port 443 and the
portal using port 8443.
|
| CYR-25920 |
Fixed an issue where authentication override values in portal and
gateway configurations were not accepted when the following
conditions applied:
|
| CYR-15091 |
Fixed an issue where extra IPSec termination nodes were allocated
to a compute location if you allocate bandwidth multiple times
in a very short time interval.
|
Prisma Access 3.2.0-h93 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-41084 | Fixed an issue where, after disabling the Cloud Identity Engine integration with Prisma Access, existing Group Mapping Settings caused an error upon commit. |
| CYR-38605 | Fixed an issue where the rebranded Strata Logging Service name of Strata Logging Service was not displaying correctly. |
| CYR-29408 | Fixed an issue where the Cloud Services plugin did not manage SDWAN devices that were deployed in Fedramp environments. |
Prisma Access 3.2.0-h90 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-39795 | Fixed an issue where, after installation of the Cloud Services plugin, an Explicit Proxy Kerberos server profile (default_server_profile) was installed by the __cloud_services user, even though Explicit Proxy was not enabled. |
Prisma Access 3.2.0-h89 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-37665 | Fixed an issue where, after migrating a tenant to a multi-tenant deployment, the Explicit_Proxy_Template was not created correctly and commit failed for the first tenant that was migrated. |
| CYR-24798 | Fixed an issue where in multi-tenant mode, there is no space between the Unallocated text and the unallocated bandwidth number in the multi-tenant bandwidth allocation window. |
| CYR-22671 | Fixed an issue where, in a multi-tenant deployment, the first tenant (the tenant you migrated) had prefixes appended to the device groups, templates, and template stacks such ar mu-dg, rn-tpl, and so forth. Only the tenants you create after you migrate the first tenant should have prefixes appended. |
Prisma Access 3.2.0-h85 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-35838 | Fixed an issue where sub-tenants were being inadvertently deprovisioned during a Panorama commit. This fix includes a plugin enhancement where subtenants will need to be explicitly deprovisioned by the Panorama admin to remove them from the Prisma Access infrastructure. |
| CYR-35811 | Fixed an issue where a Commit and Push operation was failing due to an empty subtenant ID for a newly added subtenant. |
| CYR-34966 | Fixed an issue where, when assigning Customize Per Site values for QoS for remote networks, remapped locations could not be selected or customized. |
| CYR-30610 | Fixed an issue where, in a Prisma Access multitenant deployment, Commit and Push operations were failing because subtenant IDs were not being populated correctly. |
Prisma Access 3.2.0-h78 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-37003 |
Fixed an issue where, after upgrading the Panorama that manages
Prisma Access to 10.2, multitenant deployments had one or more
sub-tenants deleted after a local commit was performed. Note
that, after you install the plugin that contains this hotfix and
delete a tenant, the tenant is deleted locally on the Panorama
but its configuration remains in the Prisma Access
infrastructure.
It is recommended that you backup your Panorama configuration
before you delete any sub-tenants.
To completely delete the tenant, reach out to your Palo Alto
Networks account representative or partner, who will contact the
SRE team and submit a request to delete the tenant from your
infrastructure.
|
Prisma Access 3.2.0-h76 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-33526 | Fixed an issue where Prisma Access attempted to fetch user attributes from Cloud Identity Engine (CIE) on every commit and push instead of just when the Directory Sync Service Group Mapping Settings configuration changed. |
Prisma Access 3.2.0-h75 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-35078 | Fixed an issue where an internal DNS domain could not be set and the following message was displayed: Invalid wildcard domain name. The domain name can have only one asterisk in the first position. |
| CYR-34966 | Fixed an issue where remapped compute locations did not display in the QoS settings for remote networks under Customize Per Site. |
| CYR-34429 | Fixed an issue where local commits were failing after an upgrade to the 4.1.0 Cloud Services plugin. |
| CYR-34053 | Fixed an issue where, after a compute location was remapped, remote network QoS settings could not be applied to the remapped compute location. |
| CYR-34118 | Fixed an issue where, if using Explicit Proxy in multitenant mode and after upgrading to 3.2.0+ plugin, Block Settings and Authentication Settings migrations did not take place. |
| CYR-33969 | Fixed an issue where a Mobile Users—GlobalProtect configuration was deleted without the plugin user having deleted the configuration. |
| CYR-33805 | Fixed an issue where the Remote Networks and Mobile Users text in the Multi Tenant creation window was misaligned and did not properly indicate which component the allocation charts were for. |
| CYR-25509 | Fixed an issue where an unsupported debug command was exposed. |
Prisma Access 3.2.0-h65 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-33844 | Fixed an issue where the following Cloud Services
plugin builds were not compatible with the following M-series
Panorama devices:
|
| CYR-33757 | Fixed an issue in the Traffic Steering Rule Source tab where clicking on a Source Address or Address-Group in the drop-down list caused an incorrect item in the list to be selected. |
| CYR-33695 | Fixed an issue where traffic steering rules could not be disabled or moved, and in other cases, a No object to edit in move handler error was encountered and no changes could be applied to the traffic steering rule. |
| CYR-32221 | Fixed an issue where, after clicking on the Connection Name of a Remote Network and then returning back to the previous page, the Peer IP Address displayed as Loading. |
| CYR-32186 | Fixed an issue where a Permission Denied error was received when attempting to delete a remote network. |
Prisma Access 3.2.0-h55 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-31541 | Fixed an issue where, when enabling Multi-Tenancy, an error occurred if the tenant name was longer than 24 characters. |
| CYR-31417 | Fixed an issue on Panorama Managed Prisma Access Multi-Tenency deployments where Prisma SD-WAN integrations with Panorama Integration Container (PIC) registration were failing. |
| CYR-31173 | Fixed an issue where, when exporting CSV data for all active mobile users, data for only 9000 users was exported instead of for all users. |
| CYR-31103 | Fixed an issue where when creating a new subnet with a new access domain, duplicate templates were created under the access domain. |
| CYR-29945 | Fixed an issue where Clientless VPN was getting enabled every time the cloud configuration was updated, causing the commit to fail. |
| CYR-27018 | Fixed an issue where the Cloud Services Plugin was not able to send dynamic updates requests using nsupdate to the external DNS server. |
| CYR-23502 | Fixed an issue where, when downloading current mobile user information from locations in the Japan Central compute location, the downloaded CSV information differed from the results obtained in the UI. |
Prisma Access 3.2.0-h42 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-31236 | Fixed an issue where the SSH Management Profiles Settings tab was missing from templates. |
| CYR-31103 | Fixed an issue where when creating a new subnet with a new access domain, duplicate templates were created under the access domain. |
| CYR-30770 | Fixed an issue where, in a multi-tenant setup when sub-tenants were changed under StatusNetwork DetailsRemote Networks, the Local IP address was not correctly showing the IP address. |
| CYR-27018 | Fixed an issue where the gp_ddns_support.log file was missing, preventing use of the DDNS feature to resolve computer names to user IP mapping associations. |
Prisma Access 3.2.0-h37 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-30428 | Fixed an issue where, in the event of the creation
of a subtenant, modification of bandwidth allocated to existing
subtenants no longer worked as expected. |
| CYR-30332 | Fixed an issue where, if you configured inbound
access, the Peer IP Address did not display in the PanoramaCloud ServicesConfigurationInbound Access Remote Networks tab. |
| CYR-30319 | Fixed an issue where the secret key generation
for a Prisma SD-WAN integration with Prisma Access failed. |
| CYR-30072 | Fixed an issue where custom device groups
that were a parent of the Explicit Proxy Device Group could not
use predefined special objects without causing a commit error. |
| CYR-29891 | Fixed an issue where, when users access the
GlobalProtect Portal without accessing the Cloud Services plugin,
the portal agent config might not be synchronized. |
| CYR-29809 | Fixed an issue where, if the user onboarded
mobile users locations and did not choose any locations to be selected
under Manual Gateway Locations tab, subsequent local commits on
the Panorama appliance was failing with the error Failed to find any locations in path: cloud_services/mobile-users/onboarding/entry/manual-gateway/region/entry/locations/memberregions validation for manual-gateway failed for Mobile Users.Failed plugin validation. |
| CYR-29464 | Fixed an issue where the Peer
IP Address did not display in a multitenant deployment. |
| CYR-27275 | Fixed an issue where the QoS profile was configured
with an Egress Max value that was higher than the bandwidth that
was allocated to a remote network location. |
Prisma Access 3.2.0-h24 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-29598 | Fixed an issue where, after upgrading the Panorama
version to 10.2.3, a local commit to Panorama took a long amount
of time (10 to 15 minutes). |
| CYR-29185 | Fixed an issue where Administrative users
who use role-based access control (RBAC) were not assigned the correct
RBAC privileges after a Cloud Services plugin upgrade. |
| CYR-28926 | Fixed an issue where Admin Role Profiles did
not have the correct administrative privileges. |
| CYR-28830 | Fixed an issue where device identification was
not being enabled on the zones. |
| CYR-28774 | Fixed an issue where, when a banner displayed
that the Panorama version is incompatible with the Cloud Services
plugin version, an incorrect URL displayed. |
| CYR-28763 | Fixed an issue where, when setting allocating
guaranteed QoS bandwidth to a value more than 500 Mbps, plugin validation
failed and an egress-guaranteed is larger than egress-max message
displayed. |
| CYR-28180 | Fixed an issue where, when multiple portals
were configured in a Mobile Users—GlobalProtect deployment, configuration details
were not synchronized for the portal using port 443 and the portal
using port 8443. |
| CYR-27952 | Fixed an issue where, when performing a bulk
configuration import for remote networks, a Failed to import IKE Gateway undefined error
is received when importing the CSV file. |
| CYR-27672 | Fixed an issue where a backup and restore
operation was not successful. |
| CYR-28685 | Fixed an incompatibility issue with using Panoramas
running 10.1.6-h6 to manage Prisma Access. |
| CYR-26516 | Fixed an issue where, when the IP Allowlist
feature has Using IP Allow List in SaaS Apps set
to Yes, the Egress IP Allowlist table was
not populated without refreshing the page. |
| CYR-26033 | Fixed an issue where, when migrating to the
bandwidth allocation model, a Migration Error window displayed with
an Error: Migration command did not create a file message. |
| CYR-23526 | Fixed an issue where, when changing the Local
IP Address in the BGP tab for a Remote Network connection that uses
BGP, the following issues could be seen:
|
| CYR-22276 | Fixed an issue where, in the Egress IP Allowlist table, newly-added IP addresses were marked as Undefined. |
Prisma Access 3.2.0-h7 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-27974 and CYR-27489 | Fixed an issue where commit validation failed
with a message that pre-prod tenants were not allowed on the current
license type on this tenant. |
| CYR-27817 | Fixed an issue where, after a Cloud Services
plugin upgrade, bulk importing of Remote Network configurations
could not be provisioned to the upgraded plugin with a Failed to load the selected configuration error
after selecting Import. |
| CYR-27558 | Fixed an issue where performing a global find
operation on the Panorama that manages Prisma Access caused a deletion
of the mobile user template and plugin configuration. |
Prisma Access 3.2.0 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-25627 | Fixed an issue where, if you had QoS enabled
in a Remote Network compute location, and you reduced the bandwidth
for a compute location enough that Prisma Access removed an IPSec
termination node from that compute location, QoS was disabled for
that compute location. |
| CYR-25402 | Fixed an issue where, when using a 10.2.2
Panorama to manage a Panorama Managed Prisma Access 3.1.2 deployment, when
attempting to download Preview Rules in the Mobile_User_Device_Group (PoliciesPreview RulesPDF/CSV), a 500 Internal Server Error is
received. |
| CYR-24033 | Fixed an issue where, when onboarding a remote
network and selecting options such as Summarize Mobile User Routes before
advertising, Enable BGP, Don't Advertise Prisma Access
Routes, or Advertise Default Route, an Object already exists error
was displayed. |
| CYR-23829 | Fixed an issue where, if you have enabled cloud
provider redundancy for service connections, the Redundancy Assessment
area in the Network Details tab (PanoramaCloud ServicesStatusNetwork DetailsService Connection) showed
(link to published locations). |
| CYR-23367 | Fixed an issue where, after migrating from
a remote network deployment that allocates bandwidth by location
to one that allocates bandwidth by compute location, QoS statistics
were not displayed for inbound access sites. |
| CYR-17694 | Fixed an issue where a global evaluation SKU
was not supported. |
| CYR-16583 | Fixed an issue where WildFire logs showed
explicit proxy logs as having a source zone of Proxy. |