I’ve previously used a mix of LDAP, RADIUS, and TACACS authentication for administrator access on Palo Alto firewalls, but have never done so without local accounts configured on each device. Since our Palo Alto VM-300s are being turned over to the larger parent company with over 20 admins, it is no longer practical to have individual accounts as we needed to control group policy / admin role centrally on the authentication server.
Still on software version 8.1.18, it was a bit confusing how to do this as there were several outdated docs but there, but eventually I found https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClIxCAK which got me on the right track.
Palo Alto Device Setup
Here’s the steps to do this on the Palo Alto device:
- If not done already, create a RADIUS or TACACS server profile
- If not done already, create an Authentication Profile
- Under Device -> Admin Roles, create a new role.
- Create or modify a test admin account, defined locally, by setting it to use that role
- After verifying roles work as expected, delete that account.
- Under Device -> Setup -> Management Tab -> Authentication Settings, set the Authentication Profile for administrative accounts that aren’t defined locally
RADIUS Server Setup
If not done so already, setup a user group to Admin role name mapping on the authentication server. In RADIUS, this is done by adding vendor-specific attribute (VSA) which maps vendor code 25461 to the Admin Role name for the appropriate group. Use Attribute number 1, format = String, and set the attribute value to the admin role name that was created above. This is similar to how the CheckPoints (vendor code 2620) operate.
Here’s an example using NPS on Windows Server 2012R2
Upon successful authentication, the authentication server will result the role name, and the user should be set to that role.
Cisco ISE (TACACS) Server Setup
The process is fundamentally the same, and can be found here:
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000PMYmCAO
Note the case is not consistent on their group names: they use “Read-Write” and “Read-only”. You can change these to whatever values you want, as long as they’re in sync.
Layer 77 