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 ForumsAuthenticationAuthenticationCannot connect to ADCannot connect to AD
Previous
 
Next
New Post
7/8/2008 12:43 AM
 

Hi guys,
Thank you for your help, very much appreciated.

I am trying to access AD but with no luck... 

I am getting the following error:
Accessing Global Catalog:
FAIL
Checking Root Domain:
OK
Accessing LDAP:
FAIL
Find all domains in network:
Could not access LDAP to obtain domains info
Logon failure: unknown user name or bad password

In know that the credentials are correct since the followgin code does run:

            DirectoryEntry entry = new DirectoryEntry("LDAP://" + my_domain, user_name,password);
            DirectorySearcher mySearcher = new DirectorySearcher(entry);

               mySearcher.Filter = "(&(objectclass=user)(SamAccountName=georgeBush))";
                results = mySearcher.FindAll();

The detailes I'm using in the DNN authentication page are:

 
 Provider ADSIAuthenticationProvider

  Authentication Type Delegation

  Root Domain: my domain

  User Name: my domain\user name

  Password: XXX

  Confirm Password: XXX

  Email Domain: empty(I also tried with value)

  Auto-login IP Address (Optional): 
FAIL
Find all domains in network:
Could not access LDAP to obtain domains info
Logon failure: unknown user name or bad password.

 

 
New Post
7/8/2008 11:03 AM
 

Two possibilities that I can see. One is that the domain needs to be entered as dc=domain, dc=com (or whatever it is). The second is that you might need to user impersonation as outlined in the documentation.

 
New Post
7/8/2008 10:09 PM
 

Thanks a lot Mike for the quick support. It's wonderfull.
I got the AD authentication set up correctly (

Accessing Global Catalog:
OK
Checking Root Domain:
OK
Accessing LDAP:
OK
Find all domains in network:
1 Domain(s):

However:

1. I am still getting the login and register links on the right hand side of the home page.
2. It doesn't seem to be doing any authentication against AD (If I try to put in my domain account credentials - DNN does not recognize it. If I just use the credentials I added when I set up DNN - it works).

What is wrong?

I set up DNN on my local machine,which is part of a domain.
The settings are:


 DotNetNuke Authentication Settings
--------------------------------------------------------------------------------
 Enabled  unchecked(I also tried to use it checked)
 Captcha unchecked


  Active Directory Settings
--------------------------------------------------------------------------------

 Accessing Global Catalog:
OK
Checking Root Domain:
OK
Accessing LDAP:
OK
Find all domains in network:
1 Domain(s):
my_domain_name
 

--------------------------------------------------------------------------------
 
 Enabled checked
 Hide Login Controls  checked
 Synchronize Role checked
  Provider    ADSIAuthenticationProvider
 Authentication Type Delegation
 Root Domain: my domain name
 User Name:  my domain user name
 Password:  my domain password
 Confirm Password: my domain password
 Email Domain: @my domain


 Auto-login IP Address (Optional): empty


Thank you Mike.
Roy

 

 
New Post
7/9/2008 1:57 AM
 

You've got both the DNN Standard disabled and you're trying to hide the AD login control so when you click on Login (up by the Login/Register on your skin) what's happening is that it's overriding the Enabled="False" on the DNN Standard as it has to display some login component there. That's why you can login with your DNN account but not your AD account. For now, until you know everything is working the way it should leave the DNN Standard Login enabled (check it) and uncheck Hide Login Controls for the AD Provider. Then when you go to login you should see two options (DNN Standard and Windows Signin). Under Windows Signin you should be able to enter your AD credentials (DOMAIN\Username and password) and get logged in with your AD account.

 
New Post
7/9/2008 10:21 PM
 
Thank you Mike.
I followed you advice and now it does seem to work correctly – it gives me two logins – Win and DNN, and I can login with both.


My final goal is not to use the DNN authentication, only the AD (since it's running in an  Intranet environment). Basically, I want DNN to recognize the user without the user needing to authenticate.

What security roles do I need to set up in AD, so that DNN will be able to associate the user with the admin role or with the host role? (I couldn’t find anywhere documentation about it).

Thanks Mike,
Roy

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationCannot connect to ADCannot connect to AD


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