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 ForumsAuthenticationAuthenticationWindows authentication in Dotnetnuke 5.1.0Windows authentication in Dotnetnuke 5.1.0
Previous
 
Next
New Post
8/6/2009 12:20 AM
 

Hello,

I was doing some R&D to check and see if windows authentication is possible in dotnetnuke 5.1.0. I have read through a lot of posts but have not found a satisfactory answer. The obvious option is to use the DNN AD module, but we have a requirement that there be a one way trusting between 2 domains to serve the intranet as well as the internet users. In dot net applications it is easily possible without writing a single line of code by just setting the windows authentication in IIS(uncheck anonymous access) on the virtual directory of the project, it takes care of the trusted domain condition and validates the users correctly against any one of the two domains, however it seems very tedious in dotnetnuke. Can someone help me with this issue ? Is it advisable to change dotnetnuke classes or usercontrol code to achieve this functionality ?

Thanks,
Gouree
 

 
New Post
8/6/2009 4:06 PM
 

While I cannot answer you on the one-way trust issue, I "can" answer you on the other part.  Yes, I have AD authentication working with DNN 5.1.1, and it is working beautifully.

 

 
New Post
8/6/2009 7:43 PM
 

gouree phatak wrote

In dot net applications it is easily possible without writing a single line of code by just setting the windows authentication in IIS(uncheck anonymous access) on the virtual directory of the project, it takes care of the trusted domain condition and validates the users correctly against any one of the two domains, however it seems very tedious in dotnetnuke.


 
WIA works the same way with DNN.  Make your changes in the web.config and you are done. 
The AD provider allows you to sync roles,create users automatically and login with a non-AD account.  But, it you want simplicity use WIA.

To test WIA locally simply set it on your Vista or XP test box.

1. Create a user in DNN matching your desktop login name under Host.
2. Clear your browser cookies and temp files.
3. Close your browser.
4. Make your web.config changes.
5. Launch DNN.
6. You should be logged in as that user with Host privs.

mikez
 

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationWindows authentication in Dotnetnuke 5.1.0Windows authentication in Dotnetnuke 5.1.0


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