User-ID

cancel
Showing results for 
Search instead for 
Did you mean: 

User-ID

L4 Transporter

When enabling user-id where does it check against to get the information to identify  the users? I have it turned on for serveral zones and it only seems to work on the VPN user-id's.

42 REPLIES 42

@jdprovine you can configure the RADIUS server to forward succesfull authentication messages as syslog to a syslog receiver (both firewall and UserID Agent can do this)

Tom Piens
PANgurus

@jdprovine,

You can do syslog forwarding or you could use RadiUID. Syslog forwarding is probably going to be the easiest solution however. 

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 .......

@reaper

 

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?

@MickBall

 

I can see all the users from my GP logins too, I think its because they are authenticated through the portal but I don't think that is same userid stuff

@jdprovine

Regarding previous post... it depends on AD server replication.....

 

i assume you have more than 1 DC so i would have at least 2 agents running and point PA to both of them. You should in my opinion also point each agent to all DC’s. The agent comes with an autodiscover option.

 

 

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.

 

anyhows... im hoping @BPry and @reaper can advise further as i only use the agent for AD and never fully understood the syslog stuff....

@MickBall

 

We have to AD domain controllers - probably be best to put and userid agent on each one - couldn't hurt LOL

The agent only needs to be on one server (not even the AD), but more is better (redundancy, less network traffic if remote sources get "read")

Syslog needs to be sent TO the agent or the firewall, they don't go and access logs remotely
Tom Piens
PANgurus

@MickBall,

You should be getting he user-id for your GP stuff; the firewall can read that directly when it passes the auth attempt. 

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!