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 ForumsAuthenticationAuthenticationAutologin Not Working W2K8 IIS7 DNN 4.8.2 AD 1.00.3Autologin Not Working W2K8 IIS7 DNN 4.8.2 AD 1.00.3
Previous
 
Next
New Post
4/3/2008 1:21 AM
 

We recently upgraded our webserver from w2k3 + iis6 to w2k8 + iis7.  After that I upgraded DNN from 4.7.x to 4.8.2 and the latest version of the AD provider.  Since then the autologin that was working before the DNN/AD upgrade is not longer working for windows users.

On the Admin->Authentication setting page, I get the all OK with the settings, but below the auto-login text area is the following error:
Error: is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Access is denied. ---> System.Runtime.InteropServices.COMException (0x80070005): Access is denied. at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) at System.DirectoryServices.DirectoryEntry.Bind() at System.DirectoryServices.DirectoryEntry.get_IsContainer() at System.DirectoryServices.DirectoryEntries.ChildEnumerator..ctor(DirectoryEntry container) at System.DirectoryServices.DirectoryEntries.GetEnumerator() at DotNetNuke.Authentication.ActiveDirectory.Settings.CheckPipelineMode() at DotNetNuke.Authentication.ActiveDirectory.Settings.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---


I put a link on the front page of DNN that goes directly to ~/DesktopModules/AuthenticationProviders/ActiveDirectory/WindowsSignin.aspx and if anyone clicks that, it logs them in just fine for a while, then they have to click it again.  The forms auth cookies are set to expire every 60 minutes(default).

The line below is uncommented in the <httpModules> section of my web.config.
<add name="Authentication" type="DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule, DotNetNuke.Authentication.ActiveDirectory" />
The WindowsSignin.aspx file is set for WindowsAuthentication and FormsAuth(defaulted) with Anon disabled.

My AppPool is running as NetworkService in ClassicMode.
I have uninstalled the AD Provider, made sure everything was gone, then reinstalled it.
I have tried deleting the cookies on my local IE, but it still does not auto-login.

Any ideas on what I'm missing?

 
New Post
4/3/2008 1:43 PM
 

I'm not seeing anything obviously out of place with your setup but the error you're getting concerns me. I've seen it before but can't remember the exact cause of it or the fix. Is there anything more in the Event Viewer on the error. Also, check the IIS logs. Are you getting redirected to WindowsSignin.aspx after you've cleared your cache/cookies?

I've been running my dev system on Vista/IIS7 for the last few months but I haven't had access to a 2008 server. I've got to leave in a couple of hours on an out of town trip and won't be back until Sunday but I will see if I can get a VPC of Server 2008 for testing.

 
New Post
4/3/2008 4:28 PM
 

It does not appear that DNN is redirecting to the WindowsSignin.aspx when a user hits the site.  That may be the problem right there.  How do I fix that?

 

Error from the event log in DNN:

ModuleId: -1
ModuleDefId: -1
FriendlyName:
ModuleControlSource:
AssemblyVersion: 04.08.02
PortalID: 0
PortalName: XXX
UserID: 1
UserName: XXX
ActiveTabID: 52
ActiveTabName: Authentication
RawURL: /Admin/Authentication/tabid/52/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: de057231-46f0-4af9-90ff-919a3390be9c
InnerException: Access is denied.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.DirectoryServices.DirectoryEntry.Bind
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Access is denied. ---> System.Runtime.InteropServices.COMException (0x80070005): Access is denied. at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) at System.DirectoryServices.DirectoryEntry.Bind() at System.DirectoryServices.DirectoryEntry.get_IsContainer() at System.DirectoryServices.DirectoryEntries.ChildEnumerator..ctor(DirectoryEntry container) at System.DirectoryServices.DirectoryEntries.GetEnumerator() at DotNetNuke.Authentication.ActiveDirectory.Settings.CheckPipelineMode() at DotNetNuke.Authentication.ActiveDirectory.Settings.Page_Load(Object sender, EventArgs e) --- End of inner exception stack trace ---
Source:
Server Name: XXX

 
New Post
4/8/2008 3:57 PM
 

So anyone have an idea how to get the authentication handler to point to windowssignin.aspx like it should?

 
New Post
4/8/2008 4:31 PM
 

It's all done in the code but it's looking like a permission issue is preventing it from automatically hitting the page. Do some checking on Failed Request Tracing Rules for IIS 7. Perhaps we can get more information through that.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAutologin Not Working W2K8 IIS7 DNN 4.8.2 AD 1.00.3Autologin Not Working W2K8 IIS7 DNN 4.8.2 AD 1.00.3


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