11-12-2020 04:39 AM
Wndows logon user name is ABC\xyz, and the user id fetched from AD group is ABC.local\xyz, and because of that the traffic is not hitting the configured rule. Any workaround to fix this?
11-12-2020 08:46 AM
Because the UserID FETCHED this information, it is coming from the AD server, and not created/caused by the FW.
Could you change the policy to match what is being received by the AD server?
That is the suggestion.
Are you using the built in UserID agent or the standalone (or both?)
11-13-2020 12:32 PM
Hi @zamiedu ,
You can override the domain detected by the group mapping. Under the group mapping profile define "user domain" to match what you have for the ip-user-mapping:
11-15-2020 10:24 PM
Usually, the domain normalization is done to normalize the domain name to NetBIOS name.
If you don't have a user domain explicitly mentioned in the authentication profile or group mapping, you can add the NetBIOS name manually as a workaround.
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!