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 ForumsAuthenticationAuthenticationUser Registration with Active DirectoryUser Registration with Active Directory
Previous
 
Next
New Post
3/30/2009 5:20 PM
 

I have installed and enabled the ActiveDirectoryProvider 1.0.4.  I have disabled the normal login dialog.

If I have configured forms authentication mode for DotNetNuke, then when a new user visits the site, the user is are eventually presented with the Login page, and the user can login using their Windows Active Directory credentials.  This will automatically add a user by the name of DOMAIN\username to the portal and log them in successfully.

However, if I have configured Windows authentication mode, then when a new user visits the site, the user's credentials get authenticated, but they do not get added to DNN.  This creates an infinite loop as the user's credentials are correctly checked against active directory, but when they try to visit the home page (for registered users only) they get redirected back to the login page.  The login page recognizes the user is valid, and redirects back to the home page.  Do I need to make WindowsSignin.aspx the home page somehow?  What is the proper way to get the user to be registered?

Thanks.

 
New Post
3/31/2009 12:06 PM
 

You don't need to set the web.config to Windows authentication to use the AD provider. In fact it's best (as you can see) if you leave it on forms authentication.

If you've got the <add name="Authentication..... /> uncommented in your web.config (the one I mentioned commenting out your other post to stop the redirect) and use forms authentication then when a user hits your site they should be automatically redirected to WindowsSignin.aspx and automatically logged in.

When it's set to WindowsAuthentication it calls the code were the redirect occurs but as part of the check it sees it's already set to Windows authentication so the actual redirect to WindowsSignin never happens and that's what causes the infinite loop.

 

 
New Post
3/31/2009 3:45 PM
 

That seems to do what I want.  There is one thing that I am surprised by though.  I am using a third party single sign on method that grants a user a Kerberos Token.  I have a user called "user a" in my active directory domain "DOMAIN".  If I log in using "usera" with usera's password, then the method you described automatically logs in and registers "usera".  If I logout of DNN, however, the only way I can log back in is with either "DOMAIN/usera" or "usera@DOMAIN".  Both cases create a distinct username in DotNetNuke.  Do you have any recommendations for restricting the canonical name of a user?

(The Windows mode uses DOMAIN\usera login.)

Maybe I can configure DNN to enforce a "username@DOMAIN" format for usernames?

 
New Post
4/1/2009 10:29 AM
 

At this point there isn't a way around that but it is something I'm looking into.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationUser Registration with Active DirectoryUser Registration with Active Directory


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