- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
02-11-2024 02:05 AM
Hey everyone!
So, we've recently made the switch from Checkpoint firewalls to Palo Alto ones, and we're still ironing out some kinks in the setup. Right now, we're focusing on setting up app control rules and such.
But here's the thing: we've hit a snag with UserID mapping. We're hooked up to our Microsoft Active Directory on-prem, and everything seems fine when users connect via GlobalProtect VPN – they show up as "domain.pt\USER". But when they connect locally from their machines, it's just "domain\USER" without the extension. This messes up our rule enforcement.
Group memberships look fine in mappings, and rules apply as they should when using GlobalProtect. It's just the local machine connections that are wonky.
I've attached some screenshots of what's going on in the logs. Any ideas on how to fix this?
Thanks!
02-15-2024 11:49 PM
Hi @NunoFacha ,
I had the same issue a long time ago. While I could not figure out how to change the domain for the User-ID agent, you can change the domain for your users mapped to groups (Group Mapping > Server Profile > Domain Setting > User Domain) and GP users (Authentication Profile > Authentication > User Domain). Then all of your users will show up as domain\USER.
Thanks,
Tom
PS If you authentication profile is SAML, you do not have the User Domain option, but should be able to change the domain in your IdP.
PSS It does appear that the User-ID agent uses the NetBIOS domain name while the LDAP server profile uses the UNC domain name. That's not consistent.
02-15-2024 11:49 PM
Hi @NunoFacha ,
I had the same issue a long time ago. While I could not figure out how to change the domain for the User-ID agent, you can change the domain for your users mapped to groups (Group Mapping > Server Profile > Domain Setting > User Domain) and GP users (Authentication Profile > Authentication > User Domain). Then all of your users will show up as domain\USER.
Thanks,
Tom
PS If you authentication profile is SAML, you do not have the User Domain option, but should be able to change the domain in your IdP.
PSS It does appear that the User-ID agent uses the NetBIOS domain name while the LDAP server profile uses the UNC domain name. That's not consistent.
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!