User-ID-Agent wrong mapping with specific IPs

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-Agent wrong mapping with specific IPs

L1 Bithead

Hello,
since a few days we see strange things with User-ID-agent.
For some specific IP-addresses there are shown wrong users. This users even are not in the internal AD, they are just external VPN users invited from Azure. But they are mapped to internal ip addresses. Even if they are not online over VPN.
When looking into Monitor - User-ID in the column "user provided by source" there is the correct user. But in the column "user" the wrong user is shown. And this is also what we see in the CLI. We've cleaned the user-cache, installed now User-ID-Agent on the domain controllers (but of course, there the correct users are shown).
Running Pan-OS 10.1.6-h3 on the firewalls.
Any ideas?

Thanks.

1 accepted solution

Accepted Solutions

Hello!
Thanks for your replies.
I rebooted the firewall-cluster but the wrong mapping appeared again.
Then I used these commands, that solved the problem.
First find the user-id with the show command, then clear the entries for this id:

show user user-ids match-user username

clear user-policy-cache uid xx
clear uid-cache uid xx
clear uid-map-cache uid xx

 

View solution in original post

2 REPLIES 2

Cyber Elite
Cyber Elite

@ChrisCon2355,

Do these users utilize any services on these internal IPs that would cause them to authenticate to the host in question? If the service is using standard Windows Auth, that might help explain why these users are showing on internal resources.

 

If the User is differentiating from the User Provided by Source, have you verified the attributes that you have configured in regards to the source? Is it possible that whatever is triggering these authentication events is using a different directory attribute that you aren't expecting, causing them to match when they shouldn't? Maybe some relayed authentication events is using the same sAMAccountName or userPrincipalName or whatever you have the Primary Username attribute setup to? 

Hello!
Thanks for your replies.
I rebooted the firewall-cluster but the wrong mapping appeared again.
Then I used these commands, that solved the problem.
First find the user-id with the show command, then clear the entries for this id:

show user user-ids match-user username

clear user-policy-cache uid xx
clear uid-cache uid xx
clear uid-map-cache uid xx

 

  • 1 accepted solution
  • 2198 Views
  • 2 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!