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/13/2010 1:22 PM
 

I am trying to use AD on 5.4.4. 

On the settings screen:

  1. The test results are all successful. 
  2. I have synchronize role unchecked.
  3. I have defined an auto-login IP range.

I have changed the web.config to Impersonate.

It works when use the URL /DesktopModules/AuthenticationService....

Auto-login does not work.

The manual login fails with the message "Login Failed. Please remember that passwords are case sensitive" and generates an exception in the event log.  

AssemblyVersion: 5.4.4
PortalID: 0
PortalName: XXXX
UserID: -1
UserName:
ActiveTabID: 40
ActiveTabName: Home
RawURL: /Login.aspx?ReturnUrl=%2fDefault.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://xxx/Login.aspx?ReturnUrl=%2fDe...
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: 569c4d03-a2f4-4c3c-8513-f83bfebc5d0e
InnerException: Object reference not set to an instance of an object.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetUser
StackTrace:
Message: System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetUser(String LoggedOnUserName, String LoggedOnPassword)
Source:
Server Name: XXX
 
Any ideas on why I get the exception, why the manual login does not work and why the auto login does not work?

Thanks,
Greg Hart

 
New Post
8/13/2010 2:50 PM
 
I have done more testing and I find the auto-login does work! This leaves me with the problem of the manual login not working and generating the exception noted in my last post. Thanks, Greg Hart
 
New Post
8/13/2010 3:21 PM
 
Quick question..... how long are your passwords? By default the web.config expects them to be 7 digits long but you can change it to make it a lower value. Also when logging in manually login as Domain\Username unless you set the default domain in the settings.
 
New Post
8/16/2010 8:20 AM
 
My password is excactly 7 characters long. Another person's is 9 characters long. I have tried with and without the domain and setting a default domain and leaving it blank. The only thing that does not work is the manual login. Anything other than the event log I can check for errors? Any logs or traces I can turn on?
 
New Post
8/16/2010 10:51 AM
 
There's no difference between automatic or manual logins other than the need to type in the credentials.

So things to consider:
  1. Are you clicking on Windows Signin when you go to the login page?
  2. Are you entering you login as Domain\Username?
  3. Are there any programs or settings on your network that might be blocking the passing of your credentials?
 
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