09-17-2023 09:48 PM
Hi,
We are using our on prem LDAP to fetch groups on the Palo. For GP authentication as well, we are using group in
1) GP Portal > Agent > Config Selection Criteria > User/User Group
2) GP Gateway > Agent > Client Settings > Config Selection Criteria
This works well with on prem LDAP. Now we are trialling out SAML with Azure. The Authentication on the SAML succeeds but GP fails to connect because the firewall cannot find the proper group for the user. After looking at logs, it looks like, when we use LDAP the user is identified as domain\username and firewall can lookup LDAP group. When using SAML authentication, the user is identified as firstname.lastname@companyname.com
Any idea how to resolve this?
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!
