topic Re: User-ID using internal global protect and Azure Active Directory in General Topics

User-ID using internal global protect and Azure Active Directory

TomDow — Sat, 02 Feb 2019 19:37:03 GMT

Hi all,

I've setup SAML SSO based authentication to global protect with Azure Active Directory. I'm wondering if i can take this a step further by using internal global protect gateways and using global protect for USER-ID?

If i did this, how would i go about setting up user based policies on the palo? effectively allowing me to allow/deny traffic based off Azure Active directory user or group?

Apologies if i've missed something obvous within the documentation.

cheers

Tom

Re: User-ID using internal global protect and Azure Active Directory

Medisked — Thu, 28 Mar 2019 11:17:21 GMT

My environment is already on Azure-AD and I have no on prem AD. There is no intent to add on premise devices if it can be avoided.
I too was wondering if I set up the SAML connection and the Palo Alto application in O365 for firewall auth and global protect VPNs if it also encapsulated User-ID if we use global protect agents internally.

Re: User-ID using internal global protect and Azure Active Directory

TomDow — Thu, 28 Mar 2019 16:52:33 GMT

Hi Medisked,

I ended up raising this as a Palo Alto support ticket.

However i think your question is slightly different to mine. When you setup a global protect agent- this agent does send USER-ID information to the firewall. You can see this by simply looking at the Monitor tab and you'll see the username against the traffic that user has created.

However what Palo Alto have confirmed is that the Group mapping settings can only be LDAP. Therefore if you have no DCs at all and your directory service is only Azure AD- there is no way to set policies within the firewall to say "user X can only go to resource Y".

Re: User-ID using internal global protect and Azure Active Directory

Marcaria-Infrastructure — Thu, 21 Nov 2019 11:34:17 GMT

We noticed that the authentication profile can also get a value for the user group. But reading the documentation, we found that PaloAlto only uses this to match authenticating users against Allow List entries and not for policies or reports.

The only thing missing is that PaloAlto allow the use of the user group that can be pass by AzureAD on Policies.