Prisma Access Addressed Issues
Table of Contents
Expand All
|
Collapse All
Prisma Access Docs
-
3.1 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.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.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 the Prisma Access 3.1.0 release:
- Prisma Access 3.1.0-h75 Addressed Issues
- Prisma Access 3.1.0-h66 Addressed Issues
- Prisma Access 3.1.0-h62 Addressed Issues
- Prisma Access 3.1.0-h50 Addressed Issues
- Prisma Access 3.1.0-h25 Addressed Issues
- Prisma Access 3.1.0-h10 Addressed Issues
- Prisma Access 3.1.0-h10 Addressed Issues
- Prisma Access 3.1.0-h3 Addressed Issues
- Prisma Access 3.1.0 Addressed Issues
- Prisma Access 3.0.0-h24 Preferred and Innovation Addressed Issues
- Prisma Access 3.0.0-h24 Preferred and Innovation Addressed Issues
- Prisma Access 3.0.0-h4 Preferred and Innovation Addressed Issues
- Prisma Access 3.0.0 Preferred and Innovation Addressed Issues
Prisma Access 3.1.0-h75 Addressed Issues
| Issue ID | Description |
|---|---|
|
CYR-30319
|
Fixed an issue where the secret key generation for a Prisma
SD-WAN integration with Prisma Access failed.
|
|
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-28685
|
Fixed an incompatibility issue with using Panoramas running
10.1.6-h6 to manage Prisma Access.
|
|
CYR-27952
|
Fixed an issue where, when performing a bulk configuration import
for remote networks, a Failed to import IKE
Gateway "undefined" error was received when
importing the CSV file.
|
|
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:
|
Prisma Access 3.1.0-h66 Addressed Issues
| Issue ID | Description |
|---|---|
CYR-27817 | Fixed an issue where, after an upgrade to the
Cloud Services plugin 3.1.0, 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 configurations. |
CYR-26876 | Fixed an issue where, if Clientless VPN
is enabled for a Mobile Users - GlobalProtect deployment, the US
East location is deselected in the mobile users Locations tab. |
CYR-24894 | Fixed an issue where the Modified and Created fields appeared
blank when viewing security policies in Mobile_User_Device_Group
in a Panorama managed Prisma Access deployment. |
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. |
Prisma Access 3.1.0-h62 Addressed Issues
| Issue ID | Description |
|---|---|
CYR-26566 | Fixed an issue where, as the result of configuring
or changing the configuration to Mobile Users—GlobalProtect settings,
Clientless VPN was enabled, which caused commit validation errors
to display and Troubleshooting Commands information to fail to be retrieved. |
CYR-26026 | Fixed an issue where an insufficient internal
timeout value was causing local commits to Panorama to fail with
a timeout error. |
CYR-25761 | Fixed an issue where logs related to Policy
Optimizer were filling up the memory reserved for logs. |
CYR-25578 | Fixed an issue where the number of Trusted
Source Addresses in the Authentication Settings (PanoramaCloud ServicesConfigurationMobile Users—Explicit ProxySettingsAuthentication Settings)
was limited to 50,000 entries (the new limit is 100,000 entries). |
| CYR-24568 | Fixed an issue where, in the Policies tab, when
you clicked the Preview Rules button, the Export button
was clickable but not exporting in PDF/CSV format. This caveat applied
to the Explicit_Proxy_Device_Group, Mobile_User_Device_Group, Remote_Network_Device_Group,
and Service_Conn_Device_Group. |
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 was
received. |
Prisma Access 3.1.0-h50 Addressed Issues
| Issue ID | Description |
|---|---|
CYR-25637 | Fixed an issue where, when enabling allow
listing for mobile user IP addresses in a candidate configuration
when the active configuration does not have allow listing enabled,
not all of the existing IP addresses were allow listed in the candidate
configuration. |
CYR-24929 | Fixed an issue where, when onboarding locations
for a Mobile User—GlobalProtect deployment, the Japan Central and
Japan South locations were not displayed in the Asia, Australia
& Japan section of the Locations tab. |
CYR-24800 | Fixed an issue where the Enable
DDNS check box was not displayed after upgrading from
a single tenant to a multitenant deployment. |
CYR-24453 | Fixed an issue where, when trying to remove
locations, existing onboarded locations could not be deselected,
or multiple locations were deselected when only a few locations
were chosen. |
CYR-24377 | Fixed an issue where the Bandwidth Usage
field was not displaying for aggregate bandwidth remote network
deployments. |
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. |
CYR-22799 | Fixed an issue where address blocks in the
RFC 6598 subnet (100.64.0.0/10) were not being blocked when configuring
the infrastructure subnet, GlobalProtect mobile user IP address
pool, or remote network or service connection static subnets. |
CYR-21462 | Fixed an issue where administrators could
add *.*, *.com, *.net, and similar wildcard URLs to bypass Explicit
Proxy authentication for all domains in custom EDL categories. |
CYR-25131 | Fixed an issue where, when setting up Autonomous
DEM in a Prisma Access multitenant deployment, bandwidth units were not
selectable and were grayed out. |
Prisma Access 3.1.0-h25 Addressed Issues
| Issue ID | Description |
|---|---|
CYR-24578 | Fixed an issue where, when renewing the certificate
you use for the GlobalProtect app and Autonomous DEM, a message
indicated that the certificate generated successfully, but a new
certificate was not created because the existing certificate was
still valid. |
CYR-24263 | Fixed an issue where DLP Data Filtering settings
were being overwritten by settings in the Cloud Services plugin. |
Prisma Access 3.1.0-h10 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-24244 | Fixed an issue where generating a certificate
using GlobalProtect App Log Collection and Autonomous DEM in the
Prisma Access UI was failing. |
| CYR-23774 | Fixed an issue where you could not add proxy
IDs in the Proxy ID tab when onboarding service connections and
remote networks. |
Prisma Access 3.1.0-h3 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-23964 | Fixed an issue where, when adding IP addresses
to the Egress IP Allowlist, an Operation Failed pop-up window displayed
with a required_ip_count unexpected here message. |
| CYR-23515 | Fixed an issue where, when migrating to an
aggregate bandwidth deployment, a There was an error while trying to migrate message was
displayed. |
| CYR-23456 | Fixed an issue where, when switching between
tenants in a multi-tenant deployment, a tenant-name is invalid message
was displayed. |
Prisma Access 3.1.0 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-23758 | Fixed an issue where, when configuring service
connections, the Manage Site did not display in the Service Connections
tab. |
| CYR-23668 | Fixed an issue where the PanoramaCloud ServicesStatusMonitor page could
not display Service Stats except Strata Logging Service. Service Stats
for Service Connection, Remote Networks, Mobile Users—GlobalProtect,
and Mobile Users—Explicit Proxy were not populated. |
| CYR-22604 | Fixed an intermittent issue where, when Security
profiles were attached to a policy, files that were downloaded across
TLS sessions decrypted by the firewall were malformed. |
| CYR-22127 | Fixed an issue where, when configuring QoS
for a newly-added site (PanoramaCloud ServicesConfigurationRemote NetworksSettingsQoS), the Allocation
Ratio displayed as NaN%. |
| CYR-21756 | Fixed an issue where, in a situation where
other locations in the same compute region had an autoscale event,
a newly-onboarded location might show a Provisioning
Status of Not Provisioned in the
Egress IP Allow List table (PanoramaCloud ServicesConfigurationMobile Users—GlobalProtect). |
| CYR-21553 | Fixed an issue where, when configuring more
than 63 HIP profiles in a Mobile Users—GlobalProtect deployment,
an error message with multiple occurrences of the word Error: was received
during commit. |
| CYR-19983 | Fixed an issue where, if you Enable
IPv6, selected the compute locations in IPv6
Availability, committed and pushed your changes, then deselected Enable IPv6,
the selections you made in the IPv6 Availability tab
became deselected. |
| CYR-19017 | Fixed an issue where IPv6-related choices
under Cloud ServicesConfigurationService ConnectionBGP were displayed,
even if IPv6 was not enabled. |
| CYR-17739 | Fixed an issue where, when configuring an
Explicit Proxy deployment, if you onboard your deployment, then
retrieve the Explicit Proxy public IP addresses, you received the active
IP addresses to add to your allow list, but did not receive the
pre-allocated backup IP addresses. |
Prisma Access 3.0.0-h24 Preferred and Innovation Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-23400 | Fixed an issue where, when migrating from
a single tenant to a multi tenant Prisma Access-Prisma SD-WAN deployment,
remote network tunnels failed during plugin upgrade from 2.0 to
3.0. |
| CYR-23378 | Fixed an issue where, when configuring QoS
for remote networks, Guaranteed Bandwidth had to be entered on a
per-site level. |
| CYR-23230 | Fixed an issue where remote network tunnels
did not migrate successfully when migrating from a single tenant
to a multi-tenant Prisma Access-Prisma SD-WAN deployment. |
| CYR-22200 | Fixed an issue where QoS profiles could not
be assigned on a per-link basis for remote networks that use multiple
ECMP tunnels. |
| CYR-22127 | Fixed an issue where, when configuring QoS
for a newly-added site (PanoramaCloud ServicesConfigurationRemote NetworksSettingsQoS), the Allocation
Ratio displayed as NaN%. |
| CYR-21754 | Fixed an issue where, when selecting Manual
Gateway Locations for a Mobile Users—GlobalProtect deployment, you
could not select all gateways, or the gateways you previously selected
did not pre-populate in the Manual Gateway Locations tab. |
| CYR-15338 | Fixed an issue where, in a multi-tenant environment,
tenant names with a period (.) in the name caused configuration
tabs to be grayed out after commit. |
Prisma Access 3.0.0-h4 Preferred and Innovation Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-19898 | Removed fields related to Network Packet Broker
from the Panorama UI in Prisma Access device groups. Network Packet
Broker is not applicable to Prisma Access deployments. |
Prisma Access 3.0.0 Preferred and Innovation Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-21875 | Fixed an issue where, after upgrading to PAN-OS
10.1, some GlobalProtect tunnels fell back to SSL instead of IPSec
due to the inadvertent encapsulation of the ICMP keepalive response
from the firewall. |
| CYR-19598 | Fixed an issue where, when using explicit proxy,
some users might experience an issue where some websites are not
able to be accessed after the ACS Cookie Lifetime has expired. |
| CYR-13662 | Fixed an issue where, after you make configuration
changes to an existing service connection or remote network connection
(for example, changing the bandwidth, region, QoS, or BGP values),
the job details in the Deployment Status page (PanoramaCloud ServicesStatusStatusDeployment StatusDetails) might display a value
of TIMEOUT, even if the job completed successfully. |