I just got TACACS+ working with my ISE deployment. Here are the steps:
1) Configure your PA Firewall following these steps: https://docs.paloaltonetworks.com/pan-os/8-0/pan-os-admin/authentication/configure-tacacs-authentica...
***Important Note #1: In step 4 of this document it specifies a role. You can use a prebuilt or a custom role, but it is critical you note the name in order to for ISE to reference the VSA configuration in your shell profile.
2) I had already configured TACACS+ device administration on my ISE deployment, so check the admin guide for those directions.
3) Add the PA firewall as a network resource on ISE. Configure, IP, name pre-shared key, and check the TACACS+ as the protocol. Create any Network Device Groups for reference in the policy.
4) Create a Palo Alto custom TACACS profile. Reference this document: https://docs.paloaltonetworks.com/pan-os/8-0/pan-os-admin/authentication/authentication-types/tacacs...
For Custom Attributes you’ll need to make the type ‘MANDATORY’, use the requisite name in the document above and the Value is whatever role you specified in the note in step one on the PANOS > Device > Admin Roles.
So an example of this would be:
TACACS Profile Custom Attribute
‘MANDATORY’ - ‘PaloAlto-Admin-Role’ - <insert firewall defined custom or default Admin Role>
5) Create a policy set that references your group of PA firewalls under conditions of the policy. Choose your identity source for authentication. For authorization, set your conditions and reference the shell profile in step 4.
This allowed me to authenticate using AD via ISE TACACS+ based on existing identities in ISE and roles set on the Palo Alto Firewall.
I kind of have this working, CLI works but GUI doesn't fully.
The PA configuration part is pretty straightforward. I've never gotten anything to work without having 'all' in the allow list in the auth profile.
For ISE, you need to create a custom Shell profile and create the necessary custom attribute that defines the role you want to assign on the PA.
The list of attributes is here: https://docs.paloaltonetworks.com/pan-os/8-0/pan-os-admin/authentication/authentication-types/tacacs...
So you could create a Shell profile with customer attrib of Type=MANDATORY, Name=PaloAlto-Admin-Role, Value=Superuser
Then create your authorization policy with your PA definitions and your AD group as conditions and apply the custom shell profile.
When I do this, an account not defined in the Administrators tab is able to log in to the CLI and do all Superuser tasks. For the GUI, the same logon shows successful in the PA logs but I just get sent back to the login page, no GUI access.
If I create the account in the Administrators tab and apply the specific tacacs policy to them, then everything works.
I've been meaning to open a ticket with TAC to address the GUI issue but haven't gotten to it yet. If I learn something from them, I'll update here.
I believe I have this working as expected now. The accounts we're using are not defined locally on the firewall, they just exist in AD.
When creating the Shell profile in ISE, I had to use 3 mandatory custom attributes:
service = PaloAlto
protocol = firewall
PaloAlto-Admin-Role = superuser (or whatever custom admin role you want to define on the firewall)
I have the tacacs authentication profile set in the authentication settings.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!