i have never tried with LDAP but i'm sure its something to do with the PA being only able to read LDAP groups and not LDAP attributes that some LDAP admins use instead of groups.
below is a link explaining this issue and a possible workaround.
it may not help you but at least give you a better understanding of whats going on.
There are many methods to collect User id information: reading Active Directory authentication logs, server sessions (drive maps), API scripts, Captive portal, syslog collection, TerminalServer sessions, GlobalProtect authentication,...
Please check out this article that highlights most of the main ways to collect user identification information and how to set it all up:
well i have only briefly browsed the document but my assumptions are as follows.
if your PA identifies its users via authentication, such as your VPN then you can use LDAP groups against those users for policies etc.
the previous link explains how to do this. but...
if your users do not auth via AD then you will not be able to map IP's to users as the LDAP server will not hold a database of user related IP's.
The PA user-id reads the security log on AD as this records users addresses when they use domain services, email, logon etc.
so I would say yes to your previous post.. But.. (again)
the user-AD agent installed seperately has config settings for EDirectory.. as wll as AD.
oops! someone has just posted previous to me so may be of better use.
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!