Ok, I want to change my 3.2 DNN setup to use Windows Authentication.  I've been spending hours trying to figure out how to put all the pieces together and I am definitely confused.  I thought the new 3.2 install would have the Authentication module already installed, it doesn't.  It does however look like the web.config has been changed to support it.

Here are the steps I took:

1.  Downloaded the Windows Authentication 3.0.13 module from http://www.tttcompany.com

2.  Installed the module.

3.  Following the old directions, I first changed the web.config.  I uncommented the

line.  I don't think anything else in the old documentation applies for the web.config.

4.  Created a new page called Authentication and dropped the Authentication module on it.

5.  Configured the module and hit Ok, got "Error: Authentication is currently unavailable"

Are these the correct steps to take so far?

I'll follow this up, it may help someone.

I realized that the module exists in admin, you don't have to add it.  So I reinstalled DNN and I set the properties on the Admin Authentication module.

I got OK for Accessing Global Catalog and Checking Root Domain and FAIL for Accessing LDAP and Find All Domains in Network.  Don't know why, all my settings look good.

So I tried logging in anyway and it seems to work.  I can log in using an AD account.  Now the problem I having is with Roles/Groups.  No AD groups were created in DNN, although I'm not sure this functionality is available yet. 

So I created a role in DNN that matches a group in AD, my AD user is in this AD group.  I created a page in DNN and assigned security to the new DNN role.  I logged in expecting to see the page and I don't.  I tried prefixing the DNN role with my domain name and still no luck.

Anyone know what I'm doing wrong?  Does the FAIL for Accessing LDAP/Find all domains have anything to do with it?

Thanks for the help.

I got OK on all four tests by uncommenting identity impersonate="true" in the web.config.

The last piece I need is the AD group checking to work.

My steps are:

1.  Wipe any DNN users.

2.  Create a DNN Security Role that matches a group in my AD.

3.  Assign that DNN role to a page.

4.  Login as a domain user that is in the AD group.

I'm expecting to see the page and I don't.  Is there a naming convention for AD groups that I'm missing?

I've tried just the group name, domain\group name, and domain/group name, all with no luck.

Part of the problem may that I'm running a domain in mixed-mode, meaning this is not a native Windows 2000 domain structure.