Hi all -

We are planning to have AD authentication for the portal we are internally developing.  I tried to configure the 'Authentication System' using Extensions would appreciate clarifications on my understanding.

My approach: I only enabled the 'DNN_ActiveDirectoryAuthentication' (the other 3 were disabled).

1) Though I enabled the 'HIDE LOGIN' option, it is forcing me to enter my network credentials (part of Active directory).  I was expecting the portal to automatically log me into the portal. Is there a way to avoid entering credentials (LOGIN)?  How do I do it?

2) I was able to successfully login using my AD credentials.  But then in the SQL SERVER database, I notice that the information is being captured in the user table (similar to what I would expect in 'Default Authentication'.  Why is this being done?  Does DNN then validate the credentials against the database after the user logs-in once?  More clarity would be greatly appreciated.

3)  Just having  'DNN_ActiveDirectoryAuthentication' enabled, does restrict the usage of  'admin' and 'host' userid (since they are set up using the 'Default Authentication' (maintained in the database).  I then changed my network userid entry in the database to 'superuser' role and able to work around.  Am I right in this approach?  Can I never use the HOST userid then?

4) We have a 2 DOMAIN setup at my workplace. These are TRUSTED Domains.  Say, Domain-A and Domain-B. I am told there are internal applications that allows users of both these Domains to access (not DNN applications).  But when I try out the DNN portal, I notice, we are only able to validate only users against the primary domain (Say, Domain-A).   It is not able to sense the users of the other domain, though they are in a Trusted domain.  How do I address this issue?

5) I have some issues in my setup of 'DotNetNuke_Community_05.01.00_Source'.  When I open the VS2008 solution, I get an error 'Unable to open the web site DotNetNuke_Community' (related to no access to IIS metabase).  I know I am an adminstrator in my development machine.

Anyways, I decided to create a WEBSITE (so that I can run this in CASSINI) and pointed to the files I extracted.   I was then able to setup the portal in CASSINI and work.  Today I then tried out to create a virtual folder in IIS (and point to the website related files) with my files and I am getting strange errors (page not found).  Is there some config settings I need to modify (not sure if CASSINI set-up changed some URL settings).  I tried the regular ASP.NET way of working in CASSINI and then move them to IIS. 

Appreciate any help!

Regards!

Hi Mike -

Thanks for your esponse! 

1) It is the DNN Login control/module!  I want to setup AD authentication and the user need not have to enter credentials.  Even if I give HIDE LOGIN CONTROLS (checkbox enabled), it is showing in my site.  I see links/articles where people have instructed how to do it in IIS.  Unfortunately, I am not able to setup DNN 5.1.0 (the version i tried - community edition) in IIS ('ScriptModule already defined error', which I have hit a road-block). 

So, I tried to setup it up in CASSINI (website) and am proceeding.  My colleague setup the same in his IIS (same download from www.dotnetnuke.com site) and it is fine on his machine (virtual folder in default web site).  I followed the links to include 'remove' in the config files to address the 'ScriptModule already defined" error, but to no avail.  I am hoping, I continue exploring in CASSINI and then setup the modified code in IIS. 

2) The DNN version is 5.1.0 (I also tried 5.1.1).  User authentication is being done against AD, but immediately, I notice the network userid/password information is being saved in the database (like the default authentication DNN has).  The Password may not be stored (When I do a FORGET password against my network id, it sends a mail with just ***** in the pwd.   But why is the user information stored?

5) Here, I am having difficulty setting up Installation in IIS (due to 'Script module error).  I am aware of changing the path in the .sln file to point to my virtual folder in IIS, but I could not get the IIS setup going.   The same download file works on my colleague's development box (in his IIS).

Thanks once again!

Sanjeev

Hi Mike -

Thanks for your help! 

This may sound pretty obvious for some, but just to help the community, for the automatic login against Active Directory, the end-user should be provided the URL to the WindowsSignin.aspx page (yoururl/DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.aspx).

This will ensure their credentials against the AD are picked up automatically and they don't have to sign-in manually.

Regards