Hello there. I have often used LDAP for much of my configurations, based on simplicity and need. As you mentioned, LDAP can do authentication, can be used for LDAP Group Mappings, etc. As you also mentioned, you have individually confirmed that authentication profiles for each type, have been configured. Now, you would need to create an Authentication Sequence, which allows each auth profile to be queried/tested. The other configuration you would want to implement is creating an service account with the following permissions: Event Log Reader (to determine/establish user to ip mappings) Server Operator (to maintain known ip mappings of those ppl using file/print share sessions) WMI Probing (if needed) to query unknown IPs that may be microsoft devices, but not picked up by the previous 2 techniques. You can configure the FW (User ID --> Group Mappings) to limit those LDAP group you want policies to be for (such as FW admins) You can enabled UserID on the trusted zone, so that the FW knows who the users are. You can create policies, based on UserID name (or group mapping) to be used at matching conditions for your policies. I would recommend the old "RTM" method of reading the admin guide on UserID. All techniques that you want and described, can be accomplished. You just need to engineer the solution to do them. What other questions can we answer for you?
... View more