We have a stand alone AD server for the intranet and drupal is setup on another server.
Can I use this module still? If I can, how should I configue and make it work?
If not, does anybody have ideas about any workarounds or which module I should turn to?

Thank you so much in advance.

Comments

kswan’s picture

kswan commented

Running AD on a different server from the Drupal install is no problem. The details of the setup depends on several factors. Almost all of the setup is handled outside of Drupal, in the webserver configuration. The README.txt file gives a basic foundation so be sure to read that. The main task in the setup is restricting access to the drupal directory and setting up AD authentication to that directory. After your webserver has authenticated a user, Drupal will accept that user without additional authentication.

The details depend on whether your Drupal server is running Windows or Linux and if your webserver is Apache or IIS.

Another point to keep in mind is that this module is not actively maintained. Configuration of this module is quite involved and requires more persistence and technical ability than most Drupal modules. That said, I am using this module and it is working perfectly for me.

wbzgatsby’s picture

wbzgatsby commented

Thank you very much kswan!

From your information, I guess all the setup will be handled on the drupal server, and there's nothing to do with the AD server, right?

Our drupal server is Windows server 2003, and IIS 6.0. I've read the README.txt and the information there is too little. It seems I will have to do some research on the IIS configuration. I appreciate it so much if you would enlighten me. :-)

kswan’s picture

kswan commented

You are correct that the configuration is on the drupal server not the AD server.

I have never configured IIS, but this link might help http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/I....

kswan’s picture

kswan commented
Status: Active » Fixed

Question answered.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.