Today I deployed a wildfire server into a small company. They run Exchange as well, backed by an ActiveDirectory, so I tried to bind WF against it as well.
It worked surprisingly well, but I had one minor issue: The layout the company used was something like this:
ou=employees;dc=example;dc=com
…ou=stuff
…u=someUser
…ou=Whatever
…u=someFunctionalUserForMailingListsOrStuff
…u=someEmployee
…u=anotherEmployee
If the graph above looks odd: I agree… Anyway, I tried to include only the real users (those directly below the employees ou) and failed, due to the hardcoded recursive search in the ldap code (In the Manager class there, iirc).
Is this usecase too far-fetched for an option here? I currently think about recompiling WF with this sinle/easy change for me, but if there’'s any interest in an option for this I could offer to create something like ldap.searchscope with base, one etc. as possible options.
Glad that you agree. I already found the line and changed it for my deployment. If some more express their interest in this I could remove the hack and make it configurable.