Configure RADIUS Authentication for a Dedicated Log Collector

Configure RADIUS authentication for a Dedicated Log Collector.
Use a RADIUS server to authenticate administrative access to the Dedicated Log Collector CLI. 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. Configure RADIUS authentication.
    Administrator accounts configured for RADIUS authentication are required to have Superuser admin role privileges to successfully configure authentication for the Dedicated Log Collector.
    1. Add a RADIUS server profile.
      The profile defines how the Dedicated Log Collector connects to the RADIUS server.
      1. Select
        Server Profiles
        a profile.
      2. Enter a
        Profile Name
        to identify the server profile.
      3. Enter a
        interval in seconds after which an authentication request times out (default is 3; range is 1–20).
      4. Select the
        Authentication Protocol
        (default is
        ) that the Dedicated Log Collector uses to authenticate to the RADIUS server.
        if the RADIUS server supports that protocol; it is more secure than
      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
          for authentication requests (default is 1812).
      6. Click
        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
        Authentication Profile
        a profile.
      2. Enter a
        to identify the authentication profile.
      3. Set the
      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
        and, in the Allow List,
        the administrators that are allowed to authenticate with this authentication profile.
      7. Click
        to save the authentication profile.
  2. Configure the authentication for the Dedicated Log Collector.
    1. Select
      Managed Collectors
      and select the Dedicated Log Collector 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 the Dedicated Log Collector.
      1. Enter the number of
        Failed Attempt
        s before a user is locked out of the Dedicated Log Collector CLI.
      2. Enter the
        Lockout Time
        , in minutes, for which the Dedicated Log Collector 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 the Dedicated Log Collector.
      5. Enter the
        Max Session Time
        the administrator can be logged in before being automatically logged out.
    4. Add the Dedicated Log Collector 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
      as both a local and Panorama administrator.
      1. Add
        and configure new administrators unique to the Dedicated Log Collector. These administrators are specific to the Dedicated Log Collector 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 Dedicated Log Collector.
    5. Click
      to save the Dedicated Log Collector authentication configuration.
  3. Commit
    and then
    Commit and Push
    your configuration changes.
  4. Log in to the Panorama CLI of the Dedicated Log Collector to verify you can successfully access the Dedicated Log Collector using the local admin user.

Recommended For You