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 ForumsAuthenticationAuthenticationLogin Failed, rememer that passwords are case sensitive!Login Failed, rememer that passwords are case sensitive!
Previous
 
Next
New Post
8/26/2008 2:44 PM
 

Hi Folks,

I have a weird issue. I have Active directory authentication set up for my dotnetnuke website. The first time when the users log in, the application automatically logs them in. When the users click "Logout" button, the login screen comes up with two options "Standard" and "Windows Login".  When i click the Windows login and enter my username/pwd credentials, i got "Login Failed, rememer that passwords are case sensitive!" .. But the password is valid (the weird thing is the application logs in successully during the first visit. it fails only when the users log out and log in back!) I tried to change the password of AD users using change password screen , the password changes successfully but not able to login using the changed password.

Can somebody throw some light on this? I have no clue of what is happening!

Thanks in advance.

Saran

 

 
New Post
8/26/2008 4:00 PM
 

No so weird an issue. Some of it is actually expected behaviour. The first time they hit the site they are directed to the httpModule that dectects that they aren't authorized and redirects them to WindowsSignin.aspx where they're logged in. A .NET cookie is created at this time so that the next time the httpModule is called (which is multiple times every page change/refresh) the login sequence is bypassed. To not do that would cause an infinite loop. If they click Logout the DNN cookie is changed to reflect that but the .NET cookie isn't. It sits there knowing that the user is using Windows Authentication until such time as it expires (under .NET 1 you could set an expiry time but .NET 2 and up doesn't allow you to though in my testing it's there for somewhere between a half hour to an hour). That leaves us with two choices. Leave things as they are now or clear authentication setting when a user logs out. The problem with the later choice is that then you'd never be able to log out (the httpModule login process would fire again immediately and log them back in again).

So in short, if the user waits a half hour to an hour they'll be logged back in again.

Now for the password failed problem you're seeing. There's usually two reasons that I've seen this happen. One is that the users are entering their user credentials properly (just Username instead of Domain\Username or Username@domain.com) or that their passwords are less than 7 characters. By default the minimum password length is set to 7 in the web.config. If yours are less than this then you can adjust it in your web.config to whatever you need (I think the variable is minPasswordLength).

 
New Post
8/26/2008 4:50 PM
 

Thanks for the reply, Mike. For the password failed problem, I've entered username and password correctly! (domain\username and password is 9 chars so not an issue.. ) donno why and how it fails.. the strange thing is even if i go thro' host login and change the password of AD users.. the changed password is not reflecting and Login Failed message keeps on popping up! Pls throw some light on this!

 
New Post
8/27/2008 12:49 AM
 

Saran...change the password in DNN isn't going to help any as it uses the password from the AD (it's a one way street so changes in DNN get overwritten by information out of the AD).

Are you using impersonation in your web.config as per the documentation? I'm thinking that it might be failing there if it can't actually pull the password property out of the AD. On automatic login the code knows that the user is attempting to connect using the account that's logged onto the computer so it just looks to see if the user exists in the AD.

I've had a few poster's have the same problem as you but I can't replicate it on any of my test installs (two different AD domains, network infrastructure, location, etc) and none of the tester's have run into it. This makes it really difficult to track down exactly what the problem is and how to fix it.

 
New Post
8/27/2008 2:25 PM
 

Hi Mike,

 

Thanks again for the reply! I tried to update my AD settings following the document link which you gave me. I went to Admin>>Authentication screen, gave values for username, password textboxes and clicked update Settings button. Then, I got the following error

Error: is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Authentication.ActiveDirectory.ADSI.Utilities.AddADSIPath(String Path, Path ADSIPath) at DotNetNuke.Authentication.ActiveDirectory.ADSI.Utilities.GetRootEntry(Path ADSIPath) at DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.GetNetworkStatus() at DotNetNuke.Authentication.ActiveDirectory.AuthenticationController.NetworkStatus() at DotNetNuke.Authentication.ActiveDirectory.Settings.UpdateSettings() --- End of inner exception stack trace ---

I think some thing is wrong with my authentication provider. I tried to uninstall it from Host>Host settings screen. I was not able to uninstall i got a different error message but the files seem to be deleted and my website become unstable. Also, I'm not able to install the AD provider 1.0.0.3 again! :(

Do you have any workaround for this?

Thanks in advance.

Saran

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationLogin Failed, rememer that passwords are case sensitive!Login Failed, rememer that passwords are case sensitive!


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