Problems with User ID after upgrade from 5.0.10 to 6.0.1

Showing results for 
Show  only  | Search instead for 
Did you mean: 

Problems with User ID after upgrade from 5.0.10 to 6.0.1

L1 Bithead

After upgrading i got no match in policy rules where "source user" is in "group include list.

All traffic bypasses the rules and will match the "stealth" rule (last rule).

Had to downgrade to 5.0.10 since we have a lot of users.

Any ideas ?

P.S i never tried 5.0.11 or 6.0.0 versions


L4 Transporter

Did you try to see the user-group / ip-user mappings in the CLI? Do you have a lot of groups in your AD and are you working with group-include lists? I have seen a case before where the Palo Alto failed to hit rules with user/group criteria after a policy install / content install, but this fixes itself after another policy push..

Kind regards

This is how it looks like in 5.0.10 !

ldap groups.PNG.png

This is how it is after upgrade to 6.0.1 !


Didnt help to do a commit or reboot


There is a known issue Bug 60677 where the Group mapping queries failed for when nested groups with long group names were searched for. The search queries showed group members to be missing. This was due to the query string (groups/nested groups) being truncated at 39 characters. This is fixed in 6.0.1.

From your update I see you had upgraded to 6.0.1 too did it help to resolve.


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!