Forum Discussion
APM AD Query Branch Rules
Hi,
We're attempting to setup APM AD query branch rules using OU.
Our details looks like this (sanitized a little): CN=username,OU=IT,OU=Departments,OU=Office,DC=domain,DC=com
The default string provided is: CN=MY_GROUP, CN=Users, DC=MY_DOMAIN
Is there an issue with using OUs? As we can't seem to get it to work. Also we've created the AAA AD server object and supplied it with credentials. However, is there anyway to actually verify this piece is working standalone?
- Michael_JenkinsCirrostratus
A couple things to check
- In your
, are you specifying which attributes you want, or leaving it default (which gets all of them).AD Query
- I'd open
and open the group object and copy the DN from there to paste into the branch rule just to make sure there's no typos or anything.AD Users and computers
- you show CN=username. This is for checking group membership for a user right?
- In your
- Amit_KarnikNimbostratus
I had a similar issue with AD query. I switched to LDAP query object and it worked. I never ended up investigating why AD query did not work.
If you do want to test AD independently you could use the adtest tool. See the following solution article: https://support.f5.com/kb/en-us/solutions/public/11000/300/sol11308.html?sr=43691247
In many cases I have relied on Wireshark traces to solve what is not working.
Best.
Recent Discussions
Related Content
* 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