This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
About bajmeera
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About bajmeera
05-25-2023
2Posts
0Likes
0Solutions
May 25, 2023Last Visited
User
Activity
User
Profile
Latest posts by bajmeera
| Subject | Views | Posted |
|---|---|---|
| 10260 | 03-17-2020 08:18 AM |
Posts I Liked
| Subject | Likes | Author | Latest Post |
|---|---|---|---|
| 1 Like | |||
| 4 Likes | |||
| 2 Likes | |||
| 3 Likes | |||
| 1 Like |
User Badges
Community Statistics
| Member Since | 07-31-2017 10:59 AM |
| Date Last Visited | 05-25-2023 03:51 PM |
| Posts | 2 |
03-17-2020
08:18 AM
I had this similar issue and engaged TAC but couldnt find any definitive root cause as to why this issue popped up after we upgraded from 7.1 to 8.1, following the two steps resolved issue for us. 1. Remove User Domain from Group Mapping 2. Removed AD Group in Portal > Agent > User/User Group Root cause is still under investigation but I suspect this has something to do with the way firewall had normalized usernames(Group Mapping) in previous OS. If the Primary Username is in User Principal Name (UPN) format, it will not be normalized in the domain\username format as in previous versions. For example, if the Primary Username is received in the UPN format, it will be displayed as username@domain , not domain\username From : https://docs.paloaltonetworks.com/pan-os/8-1/pan-os-new-features/user-id-features/support-for-multiple-username-formats
... View more
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks