Hi Mike,

No. Just the provider set as DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider

Hi.  I've been reading this thread, and I thought I might chime in.  It sounds like Lu might be trying to say that the "Root Domain" field was empty.  If so, I suspect that his site might be configured to use the native IIS Windows Authentication rather than the DNN Auth AD module.

See Ya!
Van

---

See Ya! Van

Lu:
I apologize but I can't answer that question.  I've been unable to get the account auto-creation feature to work within the DNN Auth AD module.   I'm not sure which fields get copied over from AD to DNN or the mechanics of how this process works.

Up to this point, my customer had been using native IIS windows authentication on their site, not the DNN Auth AD module.  However, we brought their site up to the latest version of DNN from DNN 4.3.5, believe it or not, and the native IIS Windows Authentication has certain limitations, so I thought that I would give the DNN Auth AD module a try.

My hat is off to Mike Horton for making such a huge contribution to the DNN community.  This guy has been updating the DNN Auth AD module and providing forum support for years in between his day job and his family.  I'm sure that his family has gotten the "short end of the stick" lots of times over the years, and I suspect that this kind of work is thankless, for the most part.  So thanks, Mike! 

Today, I'm going to install a trial version of the AD-Pro module from Glanton today, and see I'll see how that module works out.  My customer has an unusual need to authenticate to 2 unrelated LDAP sources simultaneously, and it looks like AD-Pro might support that scenario.  We'll see.

Active Directory issues are a blast!  NOT!  But at least this stuff pays the bills, right?


See Ya!
Van

---

See Ya! Van