Using GlobalProtect on multi-user server to gain User-ID visibility - possible?

[ZachHeise]

We've enjoyed using globalprotect in combination with palo alto firewall policies over the past few years to allow particular policies to only apply to particular users, who are of course identified by the user signing into the globalprotect client.

We were wondering if we could expand on this capability. We don't need VPN capability, we just want traffic from users signed into globalprotect to be tagged so it shows up in the 'monitoring' interface of the firewall web GUI as coming to/from particular users.

Would it be possible to use GlobalProtect in this way?

Can globalprotect be set up in a multi-user Windows server environment so that a single install of GP on a server could have multiple users all signed into their own 'instance' of globalprotect, so traffic from that server's IP address could be tagged so that 192.168.1.1 could have outgoing traffic tagged with users contoso\alice and contoso\bob at the same time?

And then, secondly, to have globalprotect not actually sending traffic through a VPN tunnel, but just routing as normal - all we want is the user ID tagging.

I figure this is a long shot but it would be super useful to us if it were possible.

[JoergSchuetter]

Hello @ZachHeise 

Using GP as an identity provider is possible. GP needs to "talk" with a VPN gateway on a regular base, but establishing a VPN tunnel is not required. Hence more or less the same config as for the remote users, but without the VPN part (see tab "internal" on portal config).

In addition to this, there is a component named "Terminal Server Agent". It does not work for all applications (e.g. SMB fileshare is not bound to a user). This limitation is due to the fact that it's not possible to enforce the source port for SMB.