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 ForumsAuthenticationAuthenticationAD 1.03 with DNN 4.8.2 Authenticaiton FrustrationAD 1.03 with DNN 4.8.2 Authenticaiton Frustration
Previous
 
Next
New Post
4/28/2008 11:00 PM
 

Very frustrated with the following situation.  I have spent a couple of evenings but things dont seem to be setup right.

This is an intranet scenario where I would like users to be automatically logged in when they navigate to the site.  Currently, if the navigate to windowssignin.aspx they will be logged in ok which gives me some hope that AD integration is working ok.

I would like users to be automatically logged in as soon as they navigate to the root of the intranet.  Currently, the login control is shown in the upper right.  If you select it you get 
"A critical error has occurred.
Object reference not set to an instance of an object." > error message under the bread crumbs.

If i look at the admin- event viewer i see the following error message

UserID: -1
UserName:
ActiveTabID: 36
ActiveTabName: Home
RawURL: /Home/tabid/36/ctl/Login/Default.aspx?returnurl=%2fHome%2ftabid%2f36%2fDefault.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://{IP HERE}/Home/tabid/36/Default.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: d3008ad5-a742-4804-aaef-b5de1956fa65
InnerException: Object reference not set to an instance of an object.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Modules.Admin.Authentication.Login.DisplayLoginControl
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Modules.Admin.Authentication.Login.DisplayLoginControl(AuthenticationLoginBase authLoginControl, Boolean addHeader, Boolean addFooter) at DotNetNuke.Modules.Admin.Authentication.Login.BindLogin() at DotNetNuke.Modules.Admin.Authentication.Login.ShowPanel() at DotNetNuke.Modules.Admin.Authentication.Login.Page_Load(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---
Source:

My web.config looks like this
...
 <httpModules>
      <!-- add name="Authentication" type="DotNetNuke.HttpModules.AuthenticationModule, DotNetNuke.HttpModules.Authentication" / -->
      <add name="Compression" type="DotNetNuke.HttpModules.Compression.CompressionModule, DotNetNuke.HttpModules" />
      <add name="RequestFilter" type="DotNetNuke.HttpModules.RequestFilter.RequestFilterModule, DotNetNuke.HttpModules" />
      <add name="UrlRewrite" type="DotNetNuke.HttpModules.UrlRewriteModule, DotNetNuke.HttpModules" />
      <add name="Exception" type="DotNetNuke.HttpModules.Exceptions.ExceptionModule, DotNetNuke.HttpModules" />
      <add name="UsersOnline" type="DotNetNuke.HttpModules.UsersOnline.UsersOnlineModule, DotNetNuke.HttpModules" />
      <add name="DNNMembership" type="DotNetNuke.HttpModules.Membership.MembershipModule, DotNetNuke.HttpModules" />
      <add name="Personalization" type="DotNetNuke.HttpModules.Personalization.PersonalizationModule, DotNetNuke.HttpModules" />
      <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
      <add name="Authentication" type="DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule, DotNetNuke.Authentication.ActiveDirectory" />
    </httpModules>
...

I have tried the option of hiding the login control but changing this has no effect.  I have also disabled all other authentication modules but the AD one.

So, 1.) how can I have users automatically logged in ?
       2.) how can i hide the login control in the upper right corner?

I am really at a loss as to where to look.  I have read through the documentation and followed the instructions but without any success.

Help Please

- Dave

 

 
New Post
4/29/2008 1:35 AM
 

The error your getting looks like there's a problem loading the login conrtol which is a wrapper for all of the Authentication providers (DNN, AD, LiveID, OpenID, and Cardspace) which shouldn't have an effect on whether automatic logins work or not but is still a problem so let's look at that first. Is there any point where it does work (i.e. Only DNN standard login is used)? Somewhere along the way it's trying to load a control that it can't find for some reason. Also, is this a fresh install of DNN or has it been upgraded from an older version (if so which version)?

 
New Post
4/29/2008 9:09 AM
 

When using DNN authentication everything was working good. I didnt have any problem creating users and logging in with DNN Auth.

We would like to turn off DNN authentication and only use AD Auth (without the login control) so users on the intranet are immediately logged in when they connect.

This installation was 4.8 which was upgraded to the latest version 4.8.2.  
I had installed the AD 1.03 with 4.8 but it was not enabled when performing the upgraded.  
This installation is on SQL 2005.  
Any help you can provide would be very much appreciated.  I am not sure where to look at this point.

Thanks - Dave

 

 
New Post
4/29/2008 11:45 AM
 

An upgrade from 4.8 to 4.8.2 shouldn't have caused any issues but it almost appears that it's not loading the AD portion of the login properly. Did you install it separately or as part of the 4.8 install? I'm just wondering if an error was thrown somewhere along the way (and I'm not sure what error trapping there is when installed as part of a DNN install). At this point I'd suggest either reinstalling the 1.0.3 version or installing the 1.0.4 beta (http://dnn.gmss.org).

As for the auto login. What OS is the server running and are what OS are your domain controllers running? In this thread there were a number of people and it contains the solutions that they found that worked (usually a patch from MS or a change in the IE configuration).

 
New Post
4/29/2008 12:20 PM
 

I can go ahead and install 1.0.4 beta.
Do i need to uninstall 1.0.3?

Do I need to enable DNN authentication prior to in the install?

This is running on windows 2003 and the domain controllers are windows 2003 also.

-thanks dave

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAD 1.03 with DNN 4.8.2 Authenticaiton FrustrationAD 1.03 with DNN 4.8.2 Authenticaiton Frustration


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