Re: LogonUser fails with no password in W2k3
From: Amit Rahul [MS] (arahul_at_online.microsoft.com)
Date: 05/28/04
- Next message: Ryan Menezes [MSFT]: "Re: Using 128 bit AES (CALG AES 128) to generate session keys - problem"
- Previous message: Amit Rahul [MS]: "Re: how to use Cryto API"
- In reply to: SatB: "LogonUser fails with no password in W2k3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 27 May 2004 18:09:22 -0700
You can get around this by setting the registry key "limitblankpassworduse"
in currentcontrolset\control\lsa to 0. This will let LogonUser succeed with
null password. But from security perspective its highly advisable to not do
this and rather enforce no blank password policy.
-- Thanks, Amit Rahul [MS] This posting is provided "AS IS" with no warranties, and confers no rights. "SatB" <anonymous@discussions.microsoft.com> wrote in message news:88752EB6-F983-4078-82F5-A91B7B98EAE0@microsoft.com... > Hi all, > I have an application which authenticates users by using the username and password that the user enters and trying to validate the user by calling LogonUser() API. It works fine. The only time it does not work is when a user account is created with no password in W2k3 (Windows Server 2003). However it works fine in W2k. GetLastError() in W2k3 returns 1326 (Invalid user name/bad password). I am surprised that W2k3 allows users to logon to windows without entering any password but if you try the same using the LogonUser() API it fails. Any help to work around this problem or alternate solutions will be highly appreciated. > Thanks in advance, > Sat
- Next message: Ryan Menezes [MSFT]: "Re: Using 128 bit AES (CALG AES 128) to generate session keys - problem"
- Previous message: Amit Rahul [MS]: "Re: how to use Cryto API"
- In reply to: SatB: "LogonUser fails with no password in W2k3"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|