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 ForumsAuthenticationAuthenticationSimple QuestionSimple Question
Previous
 
Next
New Post
4/10/2006 9:58 AM
 

Windows Authentication should "only" be defined for that one file, not the entire site.  One other thing you need to check is your browser settings.  In IE, you have to enable automatic authentication to get it working.  The simplist way is to make it a "trusted" or "local intranet" site.

 

 
New Post
4/10/2006 3:30 PM
 
DanBall wrote

Windows Authentication should "only" be defined for that one file, not the entire site. 

Man, I hope this isn't the only official way to get this working.  Currently, I have to use Windows auth for access to our intranet site, as it has confidential information on it, and right now I don't have another good way to keep snoopers out - folks that have domain credentials, but are not not in the department using DNN. 

I've been using the Accidental Architect's Redirector module by Michael Levy to send unauthenticated users (in the DNN sense) to the admin/security/windowssignin.aspx page.  (Thank you Michael!)  I set the module so it is only visible to unauthenticated users and the code does not redirect admin users.  I would caution anyone using it to Be Careful and read the docs - and make some docs of your own - on how you implement this module on your site, or you can lock yourself out of your site in a way that will take hacking or restoring your db to recover from.  Try it on a test instance to get the hang of it, and experiment with the adminstrative command line parameter, it is really helpful.  Bookmark a dnn login page like (yoursite)/Home/tabid/36/ctl/Login/Default.aspx before you get going with this.

One problem I see with this stragegy is if non-home pages are bookmarked.  I haven't tested putting the redirect module on every page, but I suppose I should do that. 

 

 
New Post
4/10/2006 7:19 PM
 
rfreese wrote

 

Man, I hope this isn't the only official way to get this working.  Currently, I have to use Windows auth for access to our intranet site, as it has confidential information on it, and right now I don't have another good way to keep snoopers out - folks that have domain credentials, but are not not in the department using DNN. 

No, it is not the only way.  That is the way you set it up for normal use, but in your case you're not setting it up normal.  The reason that is normally the only one with permissions set up is that the website runs under one account, usually the IUSR_HOSTNAME, or ASPNET accounts (your milage may vary).  Then, when authentication occurs, it passes it to the one file that requires it, which then forces authentication. 

I'd guess that you "shouldn't" run into problems if "all" of your users are domain users, and are properly authenticated.  Places where I can predict problems would be the initial login steps, where the user is still unathenticated, so can't access any pages.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationSimple QuestionSimple Question


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