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 ForumsAuthenticationAuthenticationWindowsSignin.aspx permissionsWindowsSignin.aspx permissions
Previous
 
Next
New Post
6/9/2009 12:56 PM
 
Hello All,

Sorry if this is a re-hash of a question that has been brought up before. In searching the forums I have found many posts with related errors but not the same issue I am having. Maybe I am not searching for the right keywords :) I have AD authentication working.. users can log in without any problems. The problem I am having is more of an annoyance and I need to get clarification of how things should be set up. Here's details of my set up:

- Windows Server 2003 R2, IIS 6
- DNN Version 04.09.04
- AD Authentication Provider 01.00.05

As I said before, the AD logins work. To make things easier for users I wanted to keep one login page, so I disabled DNN authentication. I have a couple domain accounts which have host access. I am little confused though regarding IIS permissions of the WindowsSignin.aspx. When I go through IIS Manager and clear "Anonymous Access" for that file, then I get the Windows/IE Login window with "Connecting to site.com" and the Username/Password. I can cancel that and get the following message:

"You are not authorized to view this page
....
HTTP Error 401.2 - Unauthorized: Access is denied due to server configuration."

When I retype site.com in the address bar the homepage comes up fine, and then I can login through DNN. So I figured that I would allow anonymous access to WindowsSignin.aspx, since I think that window is coming up because of the permissions. When I do that then I get the (what appears to be) typical error listed below:

"Error while processing Windows Authentication
Check your IIS settings. DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.aspx should NOT allow anonymous access"

So I am kind of stuck trying to figure out how to get rid of either of these messages. It has no affect on users ability to use our site, since they can bypass these messages and log in normally. I just think it will be an annoyance that might bring in calls to our support team because users will think there is something wrong with their computer or what they are doing. Also another note (if it is even relevant) is that with some users who will be logging into the site, their computers will not be a member of our domain, although they will be using AD accounts.
 
New Post
6/10/2009 10:44 AM
 

If you take a look at the documentation most of the answers to your questions are in there. Basically for computers on the domain you want to add the site to either the intranet or trusted sites list in your internet options (that'll stop the IIS popup from happening when you go to windowssignin.aspx).

For computers outside of the domain....you don't say whether those computers are at your physical network location or they're connecting from offsite. If it's off-site then you should be able to use the autologin IP field in the settings to set it to only computers on your internal network (anyone offsite won't be directed to windowssignin.aspx).

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationWindowsSignin.aspx permissionsWindowsSignin.aspx permissions


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