User-ID Management Setting

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

User-ID Management Setting

L4 Transporter

In the device management settings there is now a "User-ID" checkbox.  I have looked at the administrators guide but it doesn't mention it, presumably because it is fairly new.

What does this actually control, because the user-id agent on the box works fine without that checked (or seems to).  Other options such as SSH, ping etc are obviously management access protocols but user-id doesn't seem to fit in quite the same.

1 accepted solution

Accepted Solutions

L6 Presenter

That option is needed to allow communication between firewalls when a firewall is acting as a redistribution point to provide user mapping information to other PAN-OS firewalls.Also it is available for management profile.You can distribute user id information as a new feature on panos 5

View solution in original post

5 REPLIES 5

L6 Presenter

That option is needed to allow communication between firewalls when a firewall is acting as a redistribution point to provide user mapping information to other PAN-OS firewalls.Also it is available for management profile.You can distribute user id information as a new feature on panos 5

L5 Sessionator

The userid option is introduced in 5.0 and need to be enabled when you are using the agentless user id and also when distributing the mappings to other firewalls

L4 Transporter

Sorry to be obtuse, but I still don't get this.

I had agentless user-id turned on and working with my 5 DCs without this turned on, so it doesn't *appear* to prevent that working.

If it controls redistribution of the user-id information I can see why I wouldn't have noticed that, but does that then mean that I need the management addresses of the to firewalls to be included in the "permitted addresses" as well?

Thanks

The checkbox allows that specific firewall to be the agent for other firewalls. It gives you a central user-ID agent that several firewalls can use without having to deploy software agents or set up the agentless configuration on every firewall.

Hope this helps,

Greg

Not really, two specific questions then:

1) Is it needed to permit an XML API connection from an external server

2) Is it needed to replicate user ID data to the HA peer?

2a) If the answer to 2 is "yes", then does the peer firewall need to be in the permitted IPs list?

  • 1 accepted solution
  • 2658 Views
  • 5 replies
  • 0 Likes
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!