Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationusing Windows to authenticate instead of LDAP using Windows to authenticate instead of LDAP
Previous
 
Next
New Post
7/7/2009 4:44 PM
 

Hi Mike,

I have been successfully using Active Directory authentication feature on one of our clients site. But today we got a email from the clients saying:

"We have an issue that has cropped up post Active Directory migration to AD 2008 and Domain Controller name changes that occurred today.  If you notice the url is linking to Authentication Services/ActiveDirectory and is failing.  I am guessing this is using LDAP to authenticate instead of Windows and is pointed at a server name instead of an ip address as the ip addresses stayed the same but the name of the servers changed. "

I am not sure exactly what she mean and how to achieve it. Is it possible to do that? I need to retrieve Names and emailIDs from Active Directory. I need to fix it as soon as possible. I will really appreciate any help.

 

My settngs for AD connectivity are:

Enabled: True

Synchronize Role?: True

Provider: ADSIAuthenticationProvider

AuthenticationType: Delegation

Root Domain: dc=domainname,dc=com

Email Domain: @domainname.com

 

Rest of the fields are blank and with these settings the site was working perfectly fine untill clients made above mentioned changes.

Thank you very much in advance,

Divya

 

 
New Post
7/8/2009 11:53 AM
 

I'm not sure what your user is talking about either but the AD provider uses ADSI (Active Directory Services Integration(?)). I've already seen with web servers running under 2008 a need for enhanced permissions and I suspect that may also be the case here when trying to talk to an active directory on a 2008 server. Are you running impersonation in the web.config on the site? That may be the answer to the problem.

 
New Post
7/8/2009 1:15 PM
 

Thank you Mike.

Yes, I am running impersonation in web.config. This is how it looks like:

 

<!-- forms or Windows authentication -->

    <authentication mode="forms">

      <forms name=".DOTNETNUKE" protection="All" timeout="999" cookieless="UseCookies" />

    </authentication>

    <identity impersonate="true" userName="domainname\MyUsername" password="MyPassword"/>

 
What should it be instead? We still need to do windows authentication only.
 
Thank you,
Divya

 

 
New Post
7/8/2009 5:04 PM
 

I don't see any problems with the impersonation line. Any error messages that might point me in a direction of some sort?

 
New Post
7/9/2009 9:51 AM
 

Mike,

Client reported today that their problem is solved on its own. Maybe some restarts were needed on their part after the major updates. Thank you very much for your support. Atleast, I got some more information that AD 2008 should not be an issue for our DNN AD authentication functionality

Thank you once again for your support,

Divya

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationusing Windows to authenticate instead of LDAP using Windows to authenticate instead of LDAP


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out