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 Login not workingAD Login not working
Previous
 
Next
New Post
8/16/2010 11:07 AM
 
1) Yes, we are clicking on the Windows Login button before entering the user name and password. 2) Yes, we are entering the user name as Domain\Username. 3) I have no idea how to tell if there are any programs or settings on the network that may be blocking the passing of credentials. Any suggestions how I can go about this? Would program or network settings that block the passing of credentials cause an Exception in the Event Log showing the Method DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetUser failed with the Message System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetUser(String LoggedOnUserName, String LoggedOnPassword)? Thanks, Greg Hart
 
New Post
8/17/2010 9:55 AM
 

My last reply was not very readable.

The automatic login works.  Using the URL http://<DotNetNuke_Install>/DesktopModules/AuthenticationServices/ActiveDirectory/WindowsSignin.aspx works.  We only fail using the manual login module.

  1. Yes, we are clicking on the Windows Login button before entering the user name and password. 
  2. Yes, we are entering the user name as Domain\Username. 
  3. I have no idea how to tell if there are any programs or settings on the network that may be blocking the passing of credentials. Any suggestions how I can go about this?

    With no differcence between the automatic login and manual login, how could program or setting on the network prevent one from working and not the other?

    Would program or network settings that block the passing of credentials cause an Exception in the Event Log showing the Method DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetUser failed with the Message System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetUser(String LoggedOnUserName, String LoggedOnPassword)?

Are there any other logs or traces we can look at?

Without Active Directory working I have no change of getting any Corporate buy in for this product.

Thanks,
Greg Hart

 
New Post
8/17/2010 11:50 AM
 
Where it might break between manually entering your credentials vs. automatic login is if there is a program that is blocking your manually entered credentials from being passed. On automatic login it doesn't even look at your password (it can't) but rather it asks, "Who is logged onto this computer?", passes that to the AD, and if the person is a valid AD user it logs you in. On manual it has to authenticate you against the AD and if it passes it logs you in. I know in the past programs like ZoneAlarm would cause problems for students when they tried to log into school resources on their laptops. Also Symantec's Internet Security used to cause them (and me because they'd come to me about it) no end of grief.

As far as logs, tracing, etc. you don't mention what OS the server is running on. I haven't looked at Server 2008 but I know on Vista and Windows 7 (what I've developed on the last couple of years) you can turn tracing on. You could also check your IIS logs.

I apolgize for not being much help but I've never run into it working one way (automatic) but not the other way (manual) except for what I posted above about the password length. It's always been an all or nothing deal for me.
 
New Post
8/17/2010 1:58 PM
 

I am running DotNetNuke 5.4.4 on Windows Server 2003 Standard Edition Service Pack 2.

I disabled Symantec Endpoint Protection and that did not make any differernce.  I tested the AD login on both Windows Server 2003 and Windows XP Pro with the same results that I have been reporting. 

I looked at the IIS logs and did not find anything unusual there.

Could the AD Settings make a difference with this problem?  I am using Impsersonation in the web.config.  On the AD Settings, I am using Delegation Authentication Type.  I have tried other Authentication Types but they do not seem to make any difference.  I did not enter a UserName/Password in the AD Settings because that caused one or more of the checks to fail.  Could not having a UserName/Password in the AD Settings cause this problem?

Thanks,
Greg Hart

 

 
New Post
8/19/2010 2:15 PM
 
We started over with DNN 5.5.0 and that did not change a thing, we still have the same issue. 

We can only  login using Auto-Login or the WindowsSignin.aspx page.  The manual login fails every time.

I figured out how to turn on tracing for an ASP.Net application.  I have verified the form posted to the DNN Application does contain the Active Directory User Name and Password.

The Event Viewer shows the DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetUser method has failed. I find no evidence of the user attempting to login when I view the Security Events in the Windows Event Viewer on the Server, but I do find event when the Auto-Login or the WindowsSingin.aspx page is used.

How can if figure out what is failing on the Server or in the DNN application between the posting of the AD Login page and the GetUser method?

Thanks,
Greg Hart

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAD Login not workingAD Login 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