Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ForumsAuthenticationAuthenticationNot able to auto login with ADNot able to auto login with AD
Previous
 
Next
New Post
2/12/2008 12:54 AM
 
Mike Horton


Joined: 7/16/2003
Posts: 4865

Vineet, contact me offline (mhorton@telus.net) and I'll send you the file.
 
New Post
2/12/2008 8:36 AM
 
Simon Mason

Joined: 5/18/2005
Posts: 55

I've almost solved my problem. It was to do with a my user account (domain\MyUser) that seemed to be corrupted, as it was in the database but did not display in the users administration section.

I renamed to the user (domain\MyUser) to (domain\MyUserOld) in the 'aspnet_Users' and 'Users' table. Browsed to my DNN site and it authenticated me and recreated my user account. Fantastic!

Mike,
I get this message when 'Hide Login Controls?' is enabled and 'DotNetNuke Authentication Settings' is not enabled.
No providers are enabled - the standard DotNetNuke Authentication provider will be used.
Is this correct?

I still get valid domains regardless of what I type into the 'Root Domain'. AD auto login is working so I'm not too concerned.
Accessing Global Catalog:
OK
Checking Root Domain:
OK
Accessing LDAP:
OK
Find all domains in network:
3 Domain(s):
Domain.myitem.net (Domain)
Dev.Domain.myitem.net (Dev)
Apps.Domain.net (APPS)


Also, Just before the user is sucessfully logged in to the portal  this error is recorded in the event log. Any ideas?


AssemblyVersion: 04.07.00
PortalID: 1
PortalName: DEV
UserID: -1
UserName:
ActiveTabID: 237
ActiveTabName: Home
RawURL: /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; InfoPath.1; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: db913f7c-d3fa-4803-9437-e3491fa4f9c5
InnerException: Error processing AD login
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Threading.Thread.AbortInternal
StackTrace:
Message: System.Exception: Error processing AD login ---> System.Threading.ThreadAbortException: Thread was being aborted.at System.Threading.Thread.AbortInternal()at System.Threading.Thread.Abort(Object stateInfo)at System.Web.HttpResponse.End()at System.Web.HttpResponse.Redirect(String url, Boolean endResponse)at System.Web.HttpResponse.Redirect(String url)at DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule.OnAuthenticateRequest(Object s, EventArgs e)--- End of inner exception stack trace ---
Source:
Server Name: DevServer
 
New Post
2/12/2008 12:07 PM
 
Mike Horton


Joined: 7/16/2003
Posts: 4865

Hey Simon

Now I see what's happening and a little bit on Hide Login Controls.

An AD user can still login using the regular DNN authentication if their user account is already in the database and the password is the same. An enhancement request was made for the ability to hide the Windows Signin controls because it can cause confusion. Usually in situations like this a link is also provided to WindowsSiginin.aspx so that new users can still get logged in. Now, that said, the only way I could hide the controls was to trick DNN. The only way to not have the WindowsSignin tab (it looks like a button but it's actually a tab control) not show on the login screen is to disable it and under normal circumstances if the AD provider is disabled all of the AD domain information is cleared out of the database. With the information cleared out of the database means that providing links to WindowsSignin would not work nor would automatic logins. What happens when an administrator clicks "Hide Login Controls" is that the domain information is a check of what options are selected is made and if enabled is checked and Hide Login Controls is checked then the domain information is written to the database but the enabled flag is set to false. Now automatic logins and WindowsSignin.aspx still work because the domain information is in the database but when you go to login manually Windows Login doesn't appear. When you also disabled the DNN authentication then there was no manual login control available and thus the error and something I didn't account for happening.

As to the thread abort error. I put a try/catch around the code that checks to see if a redirect to WindowsSiginin.aspx is needed (that's the code that signs an AD user in). That was a mistake as the redirect causes the thread abort and has been fixed in the 01.00.03 version.
 
New Post
2/13/2008 6:48 AM
 
Simon Mason

Joined: 5/18/2005
Posts: 55

Mike,

Many thanks for you explanation. Things are much clearer now.

I have not tried 1.00.03 yet, but will give it a go later this week.

I've just come across an error when assigning roles to a user account created via the AD Provider. Normal DNN user accounts do not produce this error.

It refers to CultureInfo? The only language enabled is

English (United Kingdom) en-GB
DNN shows that the role is assigned to the user and the email does go out informing the user of the role change, but shows this error.

Thanks

ModuleId: -1
ModuleDefId: -1
FriendlyName: User Roles
ModuleControlSource: Admin/Security/SecurityRoles.ascx
AssemblyVersion: 04.07.00
PortalID: 1
PortalName: Intranet
UserID: 24
UserName: Domain\SMason
ActiveTabID: 243
ActiveTabName: User Accounts
RawURL: /Admin/UserAccounts/tabid/243/ctl/User Roles/UserId/25/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://webserver/Admin/UserAccounts/tabid/243/ctl/User%20Roles/UserId/25/Default.aspx
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; InfoPath.1; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 40be917a-d309-4e9d-8df8-6834071a6864
InnerException: String reference not set to an instance of a String. Parameter name: name
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Globalization.CultureInfo..ctor
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: String reference not set to an instance of a String. Parameter name: name ---> System.ArgumentNullException: String reference not set to an instance of a String. Parameter name: nameat System.Globalization.CultureInfo..ctor(String name, Boolean useUserOverride)at DotNetNuke.Security.Roles.RoleController.SendNotification(UserInfo objUser, RoleInfo objRole, PortalSettings PortalSettings, String Action)at DotNetNuke.Security.Roles.RoleController.AddUserRole(UserInfo objUser, RoleInfo objRole, PortalSettings PortalSettings, DateTime effDate, DateTime expDate, Int32 userId, Boolean notifyUser)at DotNetNuke.Modules.Admin.Security.SecurityRoles.cmdAdd_Click(Object sender, EventArgs e) in C:\Inetpub\wwwroot\IntranetCMS\Admin\Security\SecurityRoles.ascx.vb:line 521--- End of inner exception stack trace ---
Source: 

 
 
New Post
2/13/2008 12:03 PM
 
Mike Horton


Joined: 7/16/2003
Posts: 4865

Thanks Simon. I will have to look into that to see if I can recreate it. I'm not sure why an AD user would cause it to throw that error unless all the required user information isn't being pulled from the AD. Could you compare a DNN user and an AD user on your domain and see if there are any fields different from each other (IE: email, firstname, lastname, displayname, etc).
 
 Page 5 of 9
Previous123456...9Next 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationNot able to auto login with ADNot able to auto login with AD


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