Prisma Access
Prisma Access Addressed Issues
Table of Contents
Expand All
|
Collapse All
Prisma Access Docs
-
- 6.1 Preferred and Innovation
- 6.0 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
-
-
- 4.0 & Later
- Prisma Access China
-
-
Prisma Access Addressed Issues
| Where Can I Use This? | What Do I Need? |
|---|---|
|
|
The following topics describe issues that have been addressed in Prisma Access 6.0
and Prisma Access 6.0.1.
Prisma Access 6.0.1 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-41740 | Fixed an issue where, if there were more than 100 connectors onboarded in the same region in a short duration of time, private app access through some of the ZTNA connectors might not work. |
Prisma Access 6.0.0-h40 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-58965 | Fixed an issue where Panorama did not send the onboarding commit job to the backend when onboarding Service Connections, requiring a secondary push to properly trigger the commit job for Service Connections. |
| CYR-58852 |
Fixed an issue where Panorama commit validation workflows would
fail if a tenant's licenses had the "no_limit" string under the
service_connection local service chain information in the
license_capabilities. This occurred because the system was
attempting to convert the string to an integer.
|
| CYR-58332 | Fixed an issue where commits to GlobalProtect gateways failed with a validation error related to the `max-version` setting in the SSL-TLS service profile. |
| CYR-58134 | Fixed an issue where the Private App Access option is automatically disabled by the Cloud Services plugin when the plugin was upgraded from 5.1.0-39 to 6.0.0-11 in Panorama. When this configuration was pushed to Prisma Access, customers faced outages to critical internal applications. |
| CYR-57700 | Fixed an issue where any changes to the Cloud Services Plugin onboarding configuration on Panorama resulted in an error when the 'DEFAULT' config was missing in the GlobalProtect portal. |
| CYR-57636 | Fixed an issue where users were unable to view remote network bandwidth usage statistics on Panorama. |
| CYR-57060 | Fixed an issue where, on existing aggregate bandwidth deployments that have remote network SPNs configured and use site-based licensing, previously configured remote networks SPNs were not displayed in the Panorama UI. |
| CYR-55228 | Fixed an issue where the bulk creation of remote networks for Prisma Access multitenant failed. |
| CYR-54503 | Fixed an issue where domain configurations were not applied to mobile users during a partial commit on Panorama, while the same configurations were successfully applied to remote networks. |
| CYR-53575 |
Fixed an issue where commits for passive Panorama failed,
preventing the ability to perform a required local commit from
passive Panorama.
|
Prisma Access 6.0.0-h25 Addressed Issues
| Issue ID | Description |
|---|---|
|
CYR-56987
|
Fixed an issue where the Panorama > Cloud Services > Services
> Monitor > <location> > Status Page filter is not
working correctly. Instead of showing a status, a continuously
loading icon is displayed on the upper right.
|
|
CYR-54896
|
Fixed an issue where, when using VM Panorama 11.1.6-h4, users are
unable to create access route from Panorama.
|
Prisma Access 6.0.0-h22 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-55537 | Fixed an issue related to search fields in remote network, service connection, and mobile user templates for the Zones tab. |
| CYR-55228 | Fixed an issue where, after a bulk import of remote networks using a .csv file, a commit failure was encountered. |
| CYR-55216 | Fixed an issue where the a commit-all operation failed for a Hybrid-SWG device or platform that doesn't support the Cloud Services plugin. |
| CYR-55138 | Fixed an issue where the Aggregate Bandwidth widget was not being displayed for remote networks in the Cloud Services plugin. |
| CYR-54543 | Fixed an issue where Panorama-based forced GlobalProtect logout was failing when a logged in user had a special character in the user name or computer name. You can now have a successfully log out users or computers that have a special character in the username or computer name using the logout button on the panorama plugin for Prisma Access. |
| CYR-54428 | Fixed an issue related to the Service Connection Device Group Template Stack. |
| CYR-53485 | Fixed an issue where a GlobalProtect app log certificate, which is required for ADEM, could not be generated for Prisma Access China. |
Prisma Access 6.0.0-h11 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-55020 | Fixed an issue where the Cloud Services plugin did not display the Remote Networks and Mobile Users configuration. |
| CYR-49944 | Fixed an issue where a secondary DNS server was configured, which should not be allowed. |
| CYR-29269 | Fixed an issue to increase log the size and the number of log files for the Cloud Services plugin. |
Prisma Access 6.0.0-h9 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-54776 | Fixed an issue where BGP filtering was enabled for all tenants in a multitenant deployment that was converted from a single tenant deployment. If you have an existing Prisma Access non-multitenant deployment and convert it to a multitenant deployment, only the first tenant (the tenant you migrated) supports BGP filtering. |
| CYR-53941 | Fixed an issue where, when onboarding remote networks using configuration import in a multi-tenant deployment, an import error was seen. |
| CYR-53752 | Fixed an issue where the Cloud Services plugin's trusted endpoint value was empty when the environment variable was set to None. |
| CYR-53092 | Fixed an issue where the Panorama commit was failing when the UI attempted to generate the IoT configuration automatically in a tenant with that had Base SITE and IOT SITE SKUs. |
Prisma Access 6.0.0-h3 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-53485 | Fixed an issue where a GlobalProtect app log certificate, which is required for ADEM, could not be generated for Prisma Access China. |
Prisma Access 6.0.0 Addressed Issues
| Issue ID | Description |
|---|---|
| CYR-53726 | Fixed an isssue where, for tenants using site-based licensing for branch sites, the site license type may display as Unknown for certain branch sites within SCMMonitorBranch Sites. |
| CYR-53725 | Fixed an issue where, for tenants using site-based licensing for branch sites, the dashboard under SCMMonitorBranch Sites might be intermittently unavailable in Prisma Access locations, including Qatar, Taiwan, Indonesia, Israel, and Saudi Arabia. |
| CYR-52199 | Fixed an issue where the drop down menu for bandwidth for Clean Pipe displayed incorrect bandwidths. |
| CYR-51478 | Fixed an issue where, if you used Dynamic Privilege Access, using ZTNA Connectors without at least one service connection was not supported. |
| CYR-50707 | Fixed an issue where, if you were using IP Optimization with ZTNA Connector, Source IP Address stickiness (the ability for users to maintain the same egress IP for the same source IP address in a session) was not supported. |
| CYR-47741 | Fixed an issue where the Singapore Colo-Connect service connection went down after a dataplane upgrade to 10.2.10-h8. |
| CYR-46170 | Fixed an issue where, if you enabled DDNS and you later pushed a service subnet change to your mobile users, you must also restart the DDNS plugin on your Mobile User gateway for DDNS to pick up the change. |
| CYR-45847 | Fixed an issue where, when a service subnet was changed, it as updated on the Prisma Access GlobalProtect gateways, but the GlobalProtect tunnel went down because NAT was not correctly implemented. |
| CYR-45517 | Fixed an issue where, in the Colo-Connect tab, a read-only user was able to delete onboarding entries. |
| CYR-45341 | Fixed an issue where Commit and Push jobs to Colo-Connect Device Groups were timing out, causing VLANs to not be deleted. |
| CYR-45440 | Fixed an issue where, when configuring Admin Roles, the access information was not always saved correctly. |
| CYR-44391 | Fixed an issue where Explicit Proxy deployments in China did not support using the Cloud Identity Engine or SAML for authentication. |
| CYR-44433 | Fixed an issue where the status for Remote Network jobs that were successful can change from Success to Pending state. |
| CYR-44079 | Fixed an issue where the GlobalProtect DDNS logs were not rotating and the file size kept increasing. |
| CYR-43690 | Fixed an issue where, when attempting to modify or delete Connector IP Blocks in ZTNA Connector, the changes were not applied after a Commit and Push. |
| CYR-43062 | Fixed an issue where we did not support the 5.1 DDNS feature along with the IPv6 sinkhole service. |
| CYR-42919 | Fixed an issue where, when attempting to modify or delete Connector IP Blocks in ZTNA Connector, the changes are not applied after a Commit and Push. |
| CYR-42480 | Fixed an issue where private app access could be used in deployments only when Proxy Mode or Prisma Access Browser were enabled. |
| CYR-41838 | Fixed an issue where the egress IP address for Remote Networks - High Performance deployments displayed twice when you retrieved it using the Prisma Access API. |
| CYR-39148 | Fixed an issue where, when configuring Colo-Connect, Commit and Push operations to Colo Connect Device Groups might intermittently fail. |
| CYR-30044 |
Fixed an issue where predefined EDLs weren't being populated in
the Block Settings list in a new Explicit Proxy deployment.
|