Configure RADIUS Authentication for Panorama Administrators
Table of Contents
9.1 (EoL)
Expand all | Collapse all
-
- Determine Panorama Log Storage Requirements
-
- Setup Prerequisites for the Panorama Virtual Appliance
- Perform Initial Configuration of the Panorama Virtual Appliance
- Set Up The Panorama Virtual Appliance as a Log Collector
- Set Up the Panorama Virtual Appliance with Local Log Collector
- Set up a Panorama Virtual Appliance in Panorama Mode
- Set up a Panorama Virtual Appliance in Management Only Mode
-
- Preserve Existing Logs When Adding Storage on Panorama Virtual Appliance in Legacy Mode
- Add a Virtual Disk to Panorama on an ESXi Server
- Add a Virtual Disk to Panorama on vCloud Air
- Add a Virtual Disk to Panorama on AWS
- Add a Virtual Disk to Panorama on Azure
- Add a Virtual Disk to Panorama on Google Cloud Platform
- Add a Virtual Disk to Panorama on KVM
- Add a Virtual Disk to Panorama on Hyper-V
- Mount the Panorama ESXi Server to an NFS Datastore
-
- Increase CPUs and Memory for Panorama on an ESXi Server
- Increase CPUs and Memory for Panorama on vCloud Air
- Increase CPUs and Memory for Panorama on AWS
- Increase CPUs and Memory for Panorama on Azure
- Increase CPUs and Memory for Panorama on Google Cloud Platform
- Increase CPUs and Memory for Panorama on KVM
- Increase CPUs and Memory for Panorama on Hyper-V
- Complete the Panorama Virtual Appliance Setup
-
- Convert Your Evaluation Panorama to a Production Panorama with Local Log Collector
- Convert Your Evaluation Panorama to a Production Panorama without Local Log Collector
- Convert Your Evaluation Panorama to VM-Flex Licensing with Local Log Collector
- Convert Your Evaluation Panorama to VM-Flex Licensing without Local Log Collector
- Convert Your Production Panorama to an ELA Panorama
-
- Register Panorama
- Activate a Panorama Support License
- Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is Internet-connected
- Activate/Retrieve a Firewall Management License when the Panorama Virtual Appliance is not Internet-connected
- Activate/Retrieve a Firewall Management License on the M-Series Appliance
- Install the Panorama Device Certificate
-
- Migrate from a Panorama Virtual Appliance to an M-Series Appliance
- Migrate a Panorama Virtual Appliance to a Different Hypervisor
- Migrate from an M-Series Appliance to a Panorama Virtual Appliance
- Migrate from an M-100 Appliance to an M-500 Appliance
- Migrate from an M-100 or M-500 Appliance to an M-200 or M-600 Appliance
-
- Configure an Admin Role Profile
- Configure an Access Domain
-
- Configure a Panorama Administrator Account
- Configure Local or External Authentication for Panorama Administrators
- Configure a Panorama Administrator with Certificate-Based Authentication for the Web Interface
- Configure an Administrator with SSH Key-Based Authentication for the CLI
- Configure RADIUS Authentication for Panorama Administrators
- Configure TACACS+ Authentication for Panorama Administrators
- Configure SAML Authentication for Panorama Administrators
-
- Add a Firewall as a Managed Device
-
- Add a Device Group
- Create a Device Group Hierarchy
- Create Objects for Use in Shared or Device Group Policy
- Revert to Inherited Object Values
- Manage Unused Shared Objects
- Manage Precedence of Inherited Objects
- Move or Clone a Policy Rule or Object to a Different Device Group
- Push a Policy Rule to a Subset of Firewalls
- Manage the Rule Hierarchy
- Manage the Master Key from Panorama
- Redistribute User-ID Information to Managed Firewalls
-
- Plan the Transition to Panorama Management
- Migrate a Firewall to Panorama Management and Reuse Existing Configuration
- Migrate a Firewall to Panorama Management and Push a New Configuration
- Migrate a Firewall HA Pair to Panorama Management and Reuse Existing Configuration
- Migrate a Firewall HA Pair to Panorama Management and Push a New Configuration
- Load a Partial Firewall Configuration into Panorama
- Localize a Panorama Pushed Configuration on a Managed Firewall
-
- Add Standalone WildFire Appliances to Manage with Panorama
- Configure Basic WildFire Appliance Settings on Panorama
- Remove a WildFire Appliance from Panorama Management
-
-
- Configure a Cluster and Add Nodes on Panorama
- Configure General Cluster Settings on Panorama
- Remove a Cluster from Panorama Management
- Configure Appliance-to-Appliance Encryption Using Predefined Certificates Centrally on Panorama
- Configure Appliance-to-Appliance Encryption Using Custom Certificates Centrally on Panorama
- View WildFire Cluster Status Using Panorama
- Upgrade a Cluster Centrally on Panorama with an Internet Connection
- Upgrade a Cluster Centrally on Panorama without an Internet Connection
-
-
- Manage Licenses on Firewalls Using Panorama
-
- Supported Updates
- Schedule a Content Update Using Panorama
- Upgrade Log Collectors When Panorama Is Internet-Connected
- Upgrade Log Collectors When Panorama Is Not Internet-Connected
- Upgrade Firewalls When Panorama Is Internet-Connected
- Upgrade Firewalls When Panorama Is Not Internet-Connected
- Upgrade a ZTP Firewall
- Revert Content Updates from Panorama
-
- Preview, Validate, or Commit Configuration Changes
- Enable Automated Commit Recovery
- Compare Changes in Panorama Configurations
- Manage Locks for Restricting Configuration Changes
- Add Custom Logos to Panorama
- Use the Panorama Task Manager
- Reboot or Shut Down Panorama
- Configure Panorama Password Profiles and Complexity
-
-
- Verify Panorama Port Usage
- Resolve Zero Log Storage for a Collector Group
- Replace a Failed Disk on an M-Series Appliance
- Replace the Virtual Disk on an ESXi Server
- Replace the Virtual Disk on vCloud Air
- Migrate Logs to a New M-Series Appliance in Log Collector Mode
- Migrate Logs to a New M-Series Appliance in Panorama Mode
- Migrate Logs to a New M-Series Appliance Model in Panorama Mode in High Availability
- Migrate Logs to the Same M-Series Appliance Model in Panorama Mode in High Availability
- Migrate Log Collectors after Failure/RMA of Non-HA Panorama
- Regenerate Metadata for M-Series Appliance RAID Pairs
- Troubleshoot Registration or Serial Number Errors
- Troubleshoot Reporting Errors
- Troubleshoot Device Management License Errors
- Troubleshoot Automatically Reverted Firewall Configurations
- Complete Content Update When Panorama HA Peer is Down
- View Task Success or Failure Status
- Restore an Expired Device Certificate
- Downgrade from Panorama 9.1
End-of-Life (EoL)
Configure RADIUS Authentication for Panorama Administrators
You can use a RADIUS server to authenticate administrative
access to the Panorama web interface. You can also define Vendor-Specific Attributes (VSAs) on the
RADIUS server to manage administrator authorization. Using VSAs
enables you to quickly change the roles, access domains, and user
groups of administrators through your directory service, which is
often easier than reconfiguring settings on Panorama.
You can use a RADIUS server to authenticate administrative
access to the Panorama web interface. You can also define Vendor-Specific Attributes (VSAs) on the
RADIUS server to manage administrator authorization. Using VSAs
enables you to quickly change the roles, access domains, and user
groups of administrators through your directory service, which is
often easier than reconfiguring settings on Panorama.
You
can Import the Palo Alto Networks RADIUS dictionary into
RADIUS server to define the authentication attributes needed for
communication between Panorama and the RADIUS server.
You
can also use a RADIUS server to implement multi-factor authentication (MFA) for
administrators.
- Add
a RADIUS server profile.The profile defines how Panorama connects to the RADIUS server.
- Select PanoramaServer ProfilesRADIUS and Add a profile.
- Enter a Profile Name to identify the server profile.
- Enter a Timeout interval in
seconds after which an authentication request times out (default
is 3; range is 1–20).If you use the server profile to integrate Panorama with an MFA service, enter an interval that gives administrators enough time to respond to the authentication challenge. For example, if the MFA service prompts for a one-time password (OTP), administrators need time to see the OTP on their endpoint device and then enter the OTP in the MFA login page.
- Select the Authentication Protocol (default
is CHAP) that Panorama uses to authenticate
to the RADIUS server.Select CHAP if the RADIUS server supports that protocol; it is more secure than PAP.
- Add each RADIUS server and
enter the following:
- Name to identify the server
- RADIUS Server IP address or FQDN
- Secret/Confirm Secret (a key to encrypt usernames and passwords)
- Server Port for authentication requests (default is 1812)
- Click OK to save the server profile.
- Assign the RADIUS server profile to an authentication
profile.The authentication profile defines authentication settings that are common to a set of administrators.
- Select PanoramaAuthentication Profile and Add a profile.
- Enter a Name to identify the authentication profile.
- Set the Type to RADIUS.
- Select the Server Profile you configured.
- Select Retrieve user group from RADIUS to
collect user group information from VSAs defined on the RADIUS server.Panorama matches the group information against the groups you specify in the Allow List of the authentication profile.
- Select Advanced and, in the Allow List, Add the administrators that are allowed to authenticate with this authentication profile.
- Click OK to save the authentication profile.
- Configure Panorama to use the authentication profile
for all administrators.
- Select PanoramaSetupManagement and edit the Authentication Settings.
- Select the Authentication Profile you configured and click OK.
- Configure the roles and access domains that define authorization
settings for administrators.
- Configure an Admin Role Profile if the administrator uses a custom role instead of a predefined (dynamic) role.
- Configure an Access Domain if the administrator uses a Device Group and Template role.
- Commit your changes.Select CommitCommit to Panorama and Commit your changes.
- Configure the RADIUS server.Refer to your RADIUS server documentation for the specific instructions to perform these steps:
- Add the Panorama IP address or hostname as the RADIUS client.
- Add the administrator accounts.If the RADIUS server profile specifies CHAP as the Authentication Protocol, you must define accounts with reversibly encrypted passwords. Otherwise, CHAP authentication will fail.
- Define the vendor code for Panorama (25461) and define
the RADIUS VSAs for the role, access domain,
and user group of each administrator.When you predefine dynamic administrator roles for users, use lower-case to specify the role (for example, enter superuser, not SuperUser).
- Verify that the RADIUS server performs authentication
and authorization for administrators.
- Log in the Panorama web interface using an administrator account that you added to the RADIUS server.
- Verify that you can access only the web interface pages that are allowed for the role you associated with the administrator.
- In the Monitor, Policies, and Objects tabs, verify that you can access only the device groups that are allowed for the access domain you associated with the administrator.