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 ForumsAuthenticationAuthenticationSteps to add Windows Auth in 3.2?Steps to add Windows Auth in 3.2?
Previous
 
Next
New Post
12/10/2005 7:34 PM
 

Not sure that you are doing anything wrong in DNN. I dont have a functional AD Auth at present (trying to get 4.0 to work) but if I recall in 3.2 you could only use Domain Global security groups. Doumain local and Distribution groups did not come through (I assume on purpose). The group does need to already exist in DNN and you use only the group name.

Obviously you need the 'Synchronise roles' ticked in the Authentication tab in DNN for this to work.

 
New Post
12/13/2005 5:05 PM
 
>2. Create a DNN Security Role that matches a group in my AD.

Just for the sake of investigation, can you post what that group name is? By any chance is it more than one word, and have you tested with single and multiple word groups?

> 4. Login as a domain user that is in the AD group.
Have you checked in admin, users, manage roles for this user if you're in the role?


In my testing today, the roles/groups with single word names work - when I authenticate against AD the first time, I get added to those roles - but not to the roles that match their AD counterparts but have names with more than one word. I'm running a clean install of 3.2, and I think our AD is still in mixed mode, but I'd have to check on that.


Roberta
 
New Post
12/13/2005 7:21 PM
 
I'm totally confused now. Do you have to install tam's 3.13 AD module or is AD integration included in 3.2. What are the detailed steps to get AD integration working? Is there a new document for 3.2 AD integration?
 
New Post
12/14/2005 11:36 AM
 

Sorry that you're confused! I hope this post at ASP.NET might help?

Basically, the module is built in now, and although you can use the module from tttcompany, you don't need to, and there are probably fixes in the newer code.

Roberta

 
New Post
12/15/2005 4:11 PM
 

Hopefully I can clear up the confusion.  I have gotten everything to work, including groups.  I am not an Active Directory expert by any means but I know enough to be dangerous.

Here's what I did, hopefully this will help someone.  This is for a DNN 3.2 fresh setup.

1.  Use the Authentication module under the Admin menu. (No need to download and install the old TTT Authentication module)

Depending on your specific AD setup there are two branches to follow, the first is for a standard AD setup, the second is for a setup with legacy mixed mode authentication.

*** Branch #1 ***

2.  Log into your site as admin or host and bring up the Authentication module page.

3.  Use these settings:  Windows Auth = checked, Synchonize Roles = checked, Provider = ADSIAuthenticationProvider, Authentication Type = Delegation, Email Domain = @your_domain.  Leave the other settings blank.

4.  Hit update, you will probably get OKs on the first three but a FAIL on the last item.

5.  Close your browser.  Go to the web.config and comment in <identity impersonate="true"/> and comment in <add name="Authentication".../> under <httpModules>. 

6.  Go into IIS and right click on your DNN virtual directory.  Go to Properties and then the Directory Security tab.  Click Edit button.  Change the user name and password under Anonymous access to a user that you know has access to your AD.

7.  Find the WindowsSignin.aspx page under DotNetNuke/admin/security and bring up the Properties on it.  Go to File Security tab and click Edit button.  Uncheck Anonymous access option.

8.  Go back into your DNN site and go to the Authentication module and click Update.  You should get OK for everything and AD authentication should now work correctly.

*** Branch #2 ***

2.  Log into your site as admin or host and bring up the Authentication module page.

3.  Use these settings:  Windows Auth = checked, Synchonize Roles = checked, Provider = ADSIAuthenticationProvider, Root Domain = your domain info (i.e. dc=acme, dc=com), Username/Password = user that has access to your domain, Authentication Type = Delegation, Email Domain = @your_domain.  Leave the other settings blank.

4.  Hit update, you will probably get OKs on the first three but a FAIL on the last item.

5.  Close your browser.  Go to the web.config and comment in <identity impersonate="true"/> and comment in <add name="Authentication".../> under <httpModules>. 

6.  Go into IIS and right click on your DNN virtual directory.  Go to Properties and then the Directory Security tab.  Click Edit button.  Change the user name and password under Anonymous access to a user that you know has access to your AD.

7.  Find the WindowsSignin.aspx page under DotNetNuke/admin/security and bring up the Properties on it.  Go to File Security tab and click Edit button.  Uncheck Anonymous access option.

8.  For groups to work you need to modify the source code for the ADSI Authentication provider.  The file to change is Utilities.vb under Authentication.ADSI project.  Change the GetGroupEntryByName and GetGroupEntriesByName method so that the group is found using the default LDAP directory (LDAP://rootDSE).  Email me at mgilbert at tavilo dot com for my source or compiled assemblies.

9.  Compile the changes and put the two new assemblies (DotNetNuke.Authentication.ADSI.dll and DotNetNuke.Authentication.ADSIProvider.dll) into your DNN bin directory.

10.  Go back into your DNN site and go to the Authentication module and click Update.  You should get OK for everything and AD authentication should now work correctly.

Step #8 in Branch #2 is a pure hack but works.  Hopefully the DNN team will fix this for the next version.  Email me for source code changes or compiled assemblies at mgilbert at tavilo dot com.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationSteps to add Windows Auth in 3.2?Steps to add Windows Auth in 3.2?


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