Forum Discussion
Colt_Majkrzak1
Mar 26, 2012Nimbostratus
APM V11.1HF1 querying Active Directory
Hi Everyone,
I was wondering if anyone could shed some light on an issue I'm having with a LAB setup. I have a pretty average APM policy setup (Built from the wizard), but I'm at...
David_Stout
Mar 27, 2012Nimbostratus
I didn't have that issue with the LDAP lookup. However I did things a little differently so it could scale a little better. The LDAP query is just a simple query of (sAMAccountName=%{session.logon.last.username}) against the top level domain.
When the query is run all the session parameters get populated by the query including the memberOf attribute. If you configure the groups membership checks within the LDAP Query check then the size of the box will increase everytime you add a new group to check against. So with 100 AD Group checks you have a box that has 100 lines out of it. This doesn't look good. Instead I have moved the Group Membership check to the a SINGLE resource assign box. I have attached a couple of screenshots on how I would recommend doing it.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects