Enhanced Security Measures in Place: To ensure a safer experience, we’ve implemented additional, temporary security measures for all users.
06-03-2022 04:33 AM
Hi Community,
we got an on prem domain and were using LDAP auth for GlobalProtect.
So everything configured, LDAP Profile, Auth Profile with userdomain and Group Mapping with userdomain.
In operation, a logged in user is recognized as netbios\samlaccountname - everything fine.
Now we want to utilize our ADFS on-prem server.
We used this guide to configure it (its for Prisma, but the same approach):
Even as we configured redirect on Palo side, the server retrieves Post request, so we changed that on ADFS side and now SAML SSO works - so good so far.
The problem is:
There is no userdomain info, so our whole policyset is not matching, since the user is reported as "samaccountname" - we need "netbios\samaccountname" so that the configured LDAP group mapping is working.
Does anyone has an idea how to do that with ADFS?
I haven't really found a good tutorial or documentation for it.
That relates to the settings shown in step 4 of the posting link.
Looking really forward for any hints.
Windows Account Name as an outgoing claim looked good, but didn't work
Best Regards
Johannes
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!
