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 ForumsAuthenticationAuthenticationAuto Login using AD Authentication on DNN 05.02 not workingAuto Login using AD Authentication on DNN 05.02 not working
Previous
 
Next
New Post
6/15/2010 4:57 PM
 
Made these changes and now I can't login, even from the server itself!  I get:

HTTP Error 401.2 - Unauthorized
You are not authorized to view this page due to invalid authentication headers.
DETAILS:
Module IIS Web Core
Notification AuthenticateRequest
Handler StaticFile
Error Code 0x80070005
Requested URL http://biserver:80/intranet/
Physical Path D:\Intranet\
Logon Method Not yet determined
Logon User Not yet determined
LIKELY CAUSES:
Module IIS Web Core
Notification AuthenticateRequest
Handler StaticFile
Error Code 0x80070005
Requested URL http://biserver:80/intranet/
Physical Path D:\Intranet\
Logon Method Not yet determined
Logon User Not yet determined

 
New Post
6/15/2010 6:14 PM
 
You only need to set permissions on the WindowsSignin.aspx not on the whole site. Not sure why you're changing the permissions there as it was working but just asking for credentials when you browsed to the site. The only thing you should have to be doing is what I posted previously in the Internet Options.
 
New Post
6/15/2010 6:17 PM
 
Patrick Reddy wrote:
Hmmmm...interesting.  I don't believe the AD Provider documentation mentioned these settings.  They did mention setting authentication for the WindowsSignin.aspx page, but not on the site as a whole.  I'll change that - it is set for anonymous access currently.  But how do I set "browse" permissions on the site folder under wwwroot?  I don't see that option under the direcory's permission UI.  I see Full Control, Modify, Read....etc.

 



Add "everyone" give them read and write permissions. If they can't get to the files they can't make changes to the files. Ie they would have to get on the server itself. Then make sure u use anonymous ldap auth and then turn off accept anonymous auto in iis for the site. That's how I got mine to work.
 
New Post
6/15/2010 10:55 PM
 
Sorry...graping at straws here so I'm giving an any and all suggestions a shot.

Do I need to set my site's default page to WindowsSignIn.aspx somehow?  I merely browse to http://biserver/intranet and it takes me to the home page.  If I am on the actual server, it logs me in perfectly.

What about Authentication in IIS (and the web.config)?  At both the site level and at WindowsSignin.aspx I have it set to both Forms and Windows and ASP.NET Impersonation (with admin creds to match in web.config).

Thanks.
 
New Post
6/15/2010 11:06 PM
 
Another question Mike...

My users are not accessing this from their web site.  I will simply provide them a link or a shortcut for their desktop - maybe even ad it via  an AD Group Policy (not my department).  My question is, do they need to browse to: <DNN_INSTALL>/DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.aspx  ?
I am simply having them browse to the site via http://<servername>/sitename

Thanks.
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAuto Login using AD Authentication on DNN 05.02 not workingAuto Login using AD Authentication on DNN 05.02 not working


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