PAN-OS 10.2.3-h4 Addressed Issues
PAN-OS® 10.2.3-h4 addressed issues.
Fixed an issue where Captive Portal authentication via SAML did not work.
Fixed an issue where domain information wasn't populated in IP address-to-username matching after a successful GlobalProtect authentication using an authentication override cookie.
VM-Series firewalls on Microsoft Azure environments only) Fixed an issue where the PAN-DB engine did not start when using a VM-Series firewall Flex based CPU.
Fixed an issue where the shard count displayed by the
show log-collector-es-cluster healthCLI command was higher than the recommended limit. The recommended limit can be calculated with the formula 20*heap-memory*no-of-data-nodes.
M-700 Appliances only) A CLI command was added to check the status of each physical port of a bond1 interface.
Fixed an issue where the GlobalProtect client pre-login was successful, but the certificate authentication failed.
Fixed an issue where the push scope was displaying duplicate shared objects for each device group that were listed under the
Fixed an issue where the firewall was unable to boot up on older Intel CPUs.
Fixed an issue where GlobalProtect authentication did not work on Apple MacOS devices when the authentication method used was CIE with SAML Authentication.
Fixed an issue on Panorama where the web interface was not accessible and displayed the error
504 Gateway Not Reachabledue to the mgmtsrvr process not responding.
Fixed an issue where the
dot1qVLAN tag in ARP reply packets were not displayed.
Fixed an issue where python scripts were not working as expected.
PA-3410, PA-3420, and PA-3430 firewalls only) Increased the maximum number of security zones to 200.
Fixed an issue where template configuration for the User-ID agent was not reflected on the template stack on Panorama appliances on PAN-OS 10.2.1.
Fixed a memory leak issue related to the
Fixed an issue where firewall administrators were unable to log in to the web interface when RADIUS two-factor authentication was used.
Fixed an issue where, when high availability (HA) was enabled and a dynamic update schedule was configured, the configd process unexpectedly stopped responding during configuration commits.
Recommended For You
Recommended videos not found.