Ok i have got to jump in here as getting very interesting....
im puzzled by the syslog stuff. Assumimg rad auth is accepted and a tick in the box to syslog... how does this then relate to user ip mapping... or is this for group membership ?
just to add... we also use radius for non staff logins on GP. We have no user agent to assist with this. The palo seems to do this itsel when user id is enabled on interface/zone.
a user logs into radius as fred, we have a policy that allows fred through...
am i missing something .......
The userid agent I would install on an AD domain controller could also pull information from another server that the radius information forwarded to a syslog server or the firwall can be set up to access the syslog servers information for radius - interesting.
Does the userid agent have to be on all your domain controllers or just one?
Correct, its not using the agent but it still maps an ip to a user and works just as well as the agent when it passes a policy.
however... the downside to this is that this user will only be mapped local, so using the agent will propogate the info to all devices.
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!