Configure RADIUS Authentication
You can configure RADIUS authentication for end users and firewall or Panorama administrators. For administrators, you can use RADIUS to manage authorization (role and access domain assignments) by defining Vendor-Specific Attributes (VSAs). You can also use RADIUS to implement Multi-Factor Authentication (MFA) for administrators and end users. To enable RADIUS authentication, you must configure a RADIUS server profile that defines how the firewall or Panorama connects to the server (see Step 1 below). You then assign the server profile to an authentication profile for each set of users who require common authentication settings (see Step 5 below). What you do with the authentication profile depends on which users the RADIUS server authenticates:
- End users—Assign the authentication profile to an authentication enforcement object and assign the object to Authentication policy rules. For the full procedure, see Configure Authentication Policy.
You can also configure client systems to send RADIUS Vendor-Specific Attributes (VSAs) to the RADIUS server by assigning the authentication profile to a GlobalProtect portal or gateway. RADIUS administrators can then perform administrative tasks based on those VSAs.
- Administrative accounts with authorization managed on the RADIUS server—The following procedure describes how to configure RADIUS authentication and authorization for firewall administrators. For Panorama administrators, refer to Configure RADIUS Authentication for PanoramaAdministrators.
- Add a RADIUS
server profile.The profile defines how the firewall connects to the RADIUS server.
For redundancy, add multiple RADIUS servers in the sequence you want the firewall to use. If you have selected an EAP method, configure an authentication sequence to ensure that users will be able to successfully respond to the authentication challenge. There is no alternate authentication method with EAP: if the user fails the authentication challenge and you have not configured an authentication sequence that allows another authentication method, authentication fails.
- Select DeviceServer 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–120).If you use the server profile to integrate the firewall with an MFA service, enter an interval that gives users enough time to authenticate. For example, if the MFA service prompts for a one-time password (OTP), users 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 PEAP-MSCHAPv2) that the firewall uses
to authenticate to the RADIUS server.Depending on which factors you want to use to authenticate users within your multi-factor authentication (MFA) environment, select the appropriate authentication protocol:
- Username, password, and push (an automatically triggered out-of-band request): Supported with all authentication protocols
- Push, password, token, and PIN (when password or token or PIN are provided together): Supported with PAP, PEAP with GTC, and EAP-TTLS with PAP
- Username, password, token, and PIN, and challenge-response (when password or token or PIN are provided together): Supported with PAP and PEAP with GTC
- Add each RADIUS server and
enter the following:
- Name to identify the server
- RADIUS Server IP address or FQDN. If you use an FQDN to identify the server and you subsequently change the address, you must commit the change for the new server address to take effect.
- Secret/Confirm Secret is a key to encrypt usernames and passwords and can be up to 64 characters in length.
- Server Port for authentication requests (default is 1812)
- Click OK to save the server profile.
- If you are using PEAP-MSCHAPv2 with GlobalProtect, select Allow users to change passwords after expiry to allow GlobalProtect users to changed expired passwords to log in.
- (PEAP-MSCHAPv2, PEAP with GTC, or EAP-TTLS with PAP
only) To anonymize the user’s identity in the outer tunnel
that is created after authenticating with the server, select Make
Outer Identity Anonymous.You must configure the RADIUS server so that the entire chain allows access for anonymous users. Some RADIUS server configurations may not support anonymous outer IDs, and you may need to clear the option. When cleared, the RADIUS server transmits usernames in cleartext.
- If you select an EAP authentication method, select a Certificate Profile.
the RADIUS server profile to an authentication profile.The authentication profile defines authentication settings that are common to a set of users.
- Select DeviceAuthentication 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.The firewall 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 users and groups that are allowed to authenticate with this authentication profile.
- Click OK to save the authentication profile.
- Configure the firewall to use the authentication profile
for all administrators.
- Select DeviceSetupManagement 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.If you already defined RADIUS VSAs on the RADIUS server, the names you specify for roles and access domains on the firewall must match the VSA values.
- Configure an Admin Role Profile if the administrator uses a custom role instead of a predefined (dynamic) role.
- Configure an access domain if the firewall has more
than one virtual system:
- Select DeviceAccess Domain, Add an access domain, and enter a Name to identify the access domain.
- Add each virtual system that the administrator will access, and then click OK.
- Commit your changes to activate them on the firewall.
- Configure the RADIUS server to authenticate and authorize
administrators.Refer to your RADIUS server documentation for the specific instructions to perform these steps:
- Add the firewall IP address or hostname as the RADIUS client.
- Add the administrator accounts.
- Define the vendor code for the firewall (25461) and
define the RADIUS VSAs for the role, access
domain, and user group of each administrator.For detailed instructions, refer to the following Knowledge Base articles:
When configuring the advanced vendor options on the ACS, you must set both the Vendor Length Field Size and Vendor Type Field Size to 1. Otherwise, authentication will fail.
- For Windows 2003 Server, Windows 2008 (and later), and Cisco Secure Access Control Server (ACS) 4.0—RADIUS Vendor-Specific Attributes (VSAs)
- For Cisco ACS 5.2—Configuring Cisco ACS 5.2 for use with Palo AltoVSAs
- If you have selected an EAP method, the firewall validates the server but not the client. To ensure client validity, restrict clients by IP address or subdomain.
- Verify that the RADIUS server performs authentication
and authorization for administrators.
- Log in the firewall 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 virtual systems that are allowed for the access domain you associated with the administrator.
- In MonitorAuthentication, verify the Authentication Protocol.
- Test the connection and the validity of the certificate profile using the following CLI command:
PA-200 > test authentication authentication-profile auth-profile username <username> password <password>
Configure RADIUS Authentication for Panorama Administrators
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 ...
Device > Server Profiles > RADIUS
Device > Server Profiles > RADIUS Select Device Server Profiles RADIUS or Panorama Server Profiles RADIUS to configure settings for the Remote Authentication Dial-In User ...
Enable Delivery of GlobalProtect Endpoint VSAs to a RADIUS ...
Enable Delivery of VSAs to a RADIUS Server When communicating with portals or gateways, GlobalProtect endpoints send information that includes the endpoint IP address, operating ...
Extensible Authentication Protocol (EAP) Support for RADIUS
RADIUS authentication supports PEAP-MSCHAPv2, PEAP with GTC, or EAP-TTLS with PAP for GlobalProtect & Captive Portal authentication & admin access to the firewall & Panorama. ...
Set Up RADIUS or TACACS+ Authentication
Set Up RADIUS or TACACS+ Authentication RADIUS is a client/server protocol and software that enables remote access servers to communicate with a central server to ...
RADIUS Remote Authentication Dial-In User Service (RADIUS) is a broadly supported networking protocol that provides centralized authentication and authorization. You can configure RADIUS authentication for ...
Configure Local or External Authentication for Firewall Adm...
Configure Local or External Authentication for Firewall Administrators You can use Local Authentication and External Authentication Services to authenticate administrators who access the firewall. These ...
Configure Local or External Authentication for Panorama Adm...
Configure Local or External Authentication for Panorama Administrators You can use an external authentication service or the service that is local to Panorama to authenticate ...
Authentication Profiles and Sequences
Authentication Profiles and Sequences An authentication profile defines the authentication service that validates the login credentials of administrators when they access Panorama. The service can ...