User identification (AD)

[FabioGarcia]

Dears,

We have PA2020 implemented (w/ HA) and sometimes the user identification doesn't work well.

In the picture below we can see the following scenario

1st line - PA2020 doesn’t relates my IP w/ my user and I got blocked accessing youtube.com (rule “Block R Sociais, Videos, Audio”)

2nd line - PA2020 doesn’t relates my IP w/ my user so I could only access because of last “Allow All” (rule Permite Tudo)

3rd line - PA2020 doesn’t relates my IP w/ my user so I could only access because of last “Allow All” (rule Permite Tudo)

4th line - PA2020 recognizes my IP and relates with my user “Fabio.garcia” then I could access thru rule “Permit - Grupo TI”

Those events happend in a very short time slot... around 40 seconds....

Why PA sometimes regnizes my user, sometimes it doesnt ?

I am using 60 seconds for the update interval to identify users with my agent (AD)

Thanks in advance!!

[fcremer]

Hi all,

It seems we were able to solve the issue on our end.  We did an upgrade to 5.0.2, but that didn't solve it.  After troubleshooting with support, we found out that the log records without user info actually were caused by user information cache timeouts.  The reason that logs with and without user information were mixed had to do with the fact that we only logged on session-end.

So, what we did to resolve the problem was enable WMI probing and allow WMI requests on all client hosts.  This fixed the problem entirely.

I guess that increasing the cache timeout on the User-ID Agent would have the same effect.

The only thing we do not know and cannot find out without testing (don't have any time for that) is what the difference was between the firewalls running 4.1.6 and now 5.0.x.

Frederic