This project is read-only.

Password Supplier is not Complex Enough

Oct 31, 2011 at 3:38 PM

I see that user.cs has this error as a general catch for any password change error. How would I go about diagnosing this? According to the server Security logs, this is a failure while attempting to use a logon type of 9 (impersonation).

At this time, that's the only info I have:

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          10/31/2011 10:20:10 AM
Event ID:      4625
Task Category: Logon
Level:         Information
Keywords:      Audit Failure
User:          N/A
An account failed to log on.

 Security ID:  DOMAIN\uManage
 Account Name:  umanage
 Account Domain:  DOMAIN
 Logon ID:  0xa7797e

Logon Type:   9

Account For Which Logon Failed:
 Security ID:  NULL SID
 Account Name:  -
 Account Domain:  -

Failure Information:
 Failure Reason:  An Error occured during Logon.
 Status:   0xc000010b
 Sub Status:  0x0

Process Information:
 Caller Process ID: 0x1cc
 Caller Process Name: C:\Windows\SysWOW64\inetsrv\w3wp.exe

Network Information:
 Workstation Name: -
 Source Network Address: -
 Source Port:  -

Detailed Authentication Information:
 Logon Process:  Advapi 
 Transited Services: -
 Package Name (NTLM only): -
 Key Length:  0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
 - Transited services indicate which intermediate services have participated in this logon request.
 - Package name indicates which sub-protocol was used among the NTLM protocols.
 - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<Event xmlns="">
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
    <TimeCreated SystemTime="2011-10-31T14:20:10.015231200Z" />
    <Correlation />
    <Execution ProcessID="508" ThreadID="2136" />
    <Security />
    <Data Name="SubjectUserSid">S-1-5-21-22267991-2549619828-3905192812-3666</Data>
    <Data Name="SubjectUserName">umanage</Data>
    <Data Name="SubjectDomainName">DOMAIN</Data>
    <Data Name="SubjectLogonId">0xa7797e</Data>
    <Data Name="TargetUserSid">S-1-0-0</Data>
    <Data Name="TargetUserName">-</Data>
    <Data Name="TargetDomainName">-</Data>
    <Data Name="Status">0xc000010b</Data>
    <Data Name="FailureReason">%%2304</Data>
    <Data Name="SubStatus">0x0</Data>
    <Data Name="LogonType">9</Data>
    <Data Name="LogonProcessName">Advapi  </Data>
    <Data Name="AuthenticationPackageName">MICROSOFT_AUTHENTICATION_PACKAGE_V1_0</Data>
    <Data Name="WorkstationName">-</Data>
    <Data Name="TransmittedServices">-</Data>
    <Data Name="LmPackageName">-</Data>
    <Data Name="KeyLength">0</Data>
    <Data Name="ProcessId">0x1cc</Data>
    <Data Name="ProcessName">C:\Windows\SysWOW64\inetsrv\w3wp.exe</Data>
    <Data Name="IpAddress">-</Data>
    <Data Name="IpPort">-</Data>

Oct 31, 2011 at 4:08 PM

What are the permissions of the uManage user or better yet, what delegated permissions did you grant to it?


Oct 31, 2011 at 4:48 PM

uManage has full perms on the directory where the uManage files are stored. In AD, I delegated the entire User Container for all the Account Management functions (including InetOrgPerson) but I did not delegate all the AD structures.