I’m prototyping a replacement content system using the modx-2.0.8-pl install.
We need integration with Active Directory, so I’m trying to get modActiveDirectory add-on up and running. Of course, the install was simple using the package manager. But, there were some key parameters missing, like username (bind_dn) and password. I saw they were in the component class, so I created them. That’s about as far as I’ve gotten.
I apologize, but I don’t have the time to aggressively test out the code behind this add-on beyond doing a drag and drop (or package install, really) into the system. I feel the documentation is a little thin (many apologies and no personal criticism meant!) and there’s definitely no explanation of how the add-on interacts with the built in authentication mechanism. For example, is there failover for users not in Active Directory? Do users need to be populated in the system and they simply authenticate against AD? Who knows?
I did enable the add-on and I can still only login with the users created in MODX. I can’t authenticate users in AD who are not in MODX.
Okay...got it working.
My main problem was not having enough time to look over the code to get this working (I’m wearing too many hats at present). I carved out some time and got the functionality to kick in.
It looks like if you use modActiveDirectory out of the box, it works. My error was looking too much into the admin binding for lookups. I saw in the code that an admin binding variables were available, so I added those settings to the plugin. After noting that the default internal rebind variable was killing the subsequent user bind I just got rid of the admin bindings and everything worked. I read a little too much into the setup. For the record, our AD isn’t setup for anonymous binding so extended lookups would require an admin bind. It looks like that does work if you adjust the rebind parameter in the plugin’s class file.
