>
    Strata Copilot
    Configure RADIUS Authentication for a WildFire Cluster
    Focus
    Download PDF
    Focus
    1. Home
    2. Panorama
    3. Manage WildFire Appliances
    4. Manage WildFire Clusters
    5. Configure a Cluster Centrally on Panorama
    6. Configure Authentication for a WildFire Cluster
    7. Configure RADIUS Authentication for a WildFire Cluster
    Download PDF
    Panorama

    Configure RADIUS Authentication for a WildFire Cluster

    Table of Contents

    Configure RADIUS Authentication for a WildFire Cluster

    Configure RADIUS authentication for all WildFire appliance in a WildFire cluster.
    Use a RADIUS server to authenticate administrative access to the CLI of the WildFire appliances in a WildFire cluster. 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 the Panorama™ management server.
    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.
    1. Log in to the Panorama web interface.
    2. Configure a Cluster Centrally on Panorama.
    3. Configure RADIUS authentication.
      Administrator accounts configured for RADIUS authentication are required to have Superuser admin role privileges to successfully configure authentication for Wildfire appliances in the WildFire cluster.
      1. Add a RADIUS server profile.
        The profile defines how the WildFire appliances in the WildFire clust connect to the RADIUS server.
        1. Select PanoramaServer ProfilesRADIUS and Add a profile.
        2. Enter a Profile Name to identify the server profile.
        3. Enter a Timeout interval in seconds after which an authentication request times out (default is 3; range is 1–20).
        4. Select the Authentication Protocol (default is CHAP) that a WildFire appliance uses to authenticate to the RADIUS server.
          Select CHAP if the RADIUS server supports that protocol; it is more secure than PAP.
        5. Add each RADIUS server and enter the following:
          1. Name to identify the server.
          2. RADIUS Server IP address or FQDN.
          3. Secret/Confirm Secret (a key to encrypt usernames and passwords).
          4. Server Port for authentication requests (default is 1812).
        6. Click OK to save the server profile.
      2. Assign the RADIUS server profile to an authentication profile.
        The authentication profile defines authentication settings that are common to a set of administrators.
        1. Select PanoramaAuthentication Profile and Add a profile.
        2. Enter a Name to identify the authentication profile.
        3. Set the Type to RADIUS.
        4. Select the Server Profile you configured.
        5. 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.
        6. Select Advanced and, in the Allow List, Add the administrators that are allowed to authenticate with this authentication profile.
        7. Click OK to save the authentication profile.
    4. Configure the authentication for the WildFire cluster.
      1. Select PanoramaManaged WildFire Clusters and select the WildFire cluster you previously added.
      2. Select the Authentication Profile you configured in the previous step.
        If a global authentication profile is not assigned you must assign an authentication profile to each individual local administrator to leverage remote authentication.
      3. Configure the authentication Timeout Configuration for a WildFire appliance.
        1. Enter the number of Failed Attempts before a user is locked out of a WildFire appliance CLI.
        2. Enter the Lockout Time, in minutes, for which a WildFire appliance locks out a user account after that user reaches the configured number of Failed Attempts.
        3. Enter the Idle Timeout, in minutes, before the user account is automatically logged out due to inactivity.
        4. Enter the Max Session Count to set how many user accounts can simultaneously access a WildFire appliance.
        5. Enter the Max Session Time the administrator can be logged in before being automatically logged out.
      4. Add the WildFire appliance administrators.
        Administrators may either be added as a local administrator or as an imported Panorama administrator—but not both. Adding the same administrator as both a local administrator and as an imported Panorama administrator is not supported and causes the Panorama commit to fail. For example, the commit to Panorama fails if you add admin1 as both a local and Panorama administrator.
        1. Add and configure new administrators unique to the WildFire appliances in the WildFire cluster. These administrators are specific to the WildFire appliances in the WildFire cluster for which they are created and you manage these administrators from this table.
        2. Add any administrators configured on Panorama. These administrators are created on Panorama and imported to the WildFire appliances in the WildFire cluster.
      5. Click OK to save the WildFire cluster authentication configuration.
    5. Commit and then Commit and Push your configuration changes.
    6. Access the WildFire appliance CLI to verify you can successfully access a WildFire appliance using the local admin user.

    © 2026 Palo Alto Networks, Inc. All rights reserved.