Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-6483

"puppet resource user", when run in Windows creates a login attempt.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.6.0
    • Component/s: None
    • Template:
    • Acceptance Criteria:
      Hide

      Verify that there are no audit log entries after running puppet resource user

      Show
      Verify that there are no audit log entries after running puppet resource user
    • Story Points:
      2
    • Sprint:
      Windows 2016-08-10

      Description

      When running "puppet resource user" in Windows, the action results in a log entry in the Windows security log:

      Log Name: Security
      Source: Microsoft-Windows-Security-Auditing
      Date: 7/8/2016 10:26:11 PM
      Event ID: 4625
      Task Category: Logon
      Level: Information
      Keywords: Audit Failure
      User: N/A
      Computer: pe-201612-agent-win2008
      Description:
      An account failed to log on.

      Subject:
      Security ID: PE-201612-AGENT\vagrant
      Account Name: vagrant
      Account Domain: PE-201612-AGENT
      Logon ID: 0xf07a

      Logon Type: 3

      Account For Which Logon Failed:
      Security ID: NULL SID
      Account Name: vagrant
      Account Domain: PE-201612-AGENT

      Failure Information:
      Failure Reason: Unknown user name or bad password.
      Status: 0xc000006d
      Sub Status: 0xc000006a

      Process Information:
      Caller Process ID: 0x538
      Caller Process Name: C:\Program Files\Puppet Labs\Puppet\sys\ruby\bin\ruby.exe

      Network Information:
      Workstation Name: PE-201612-AGENT
      Source Network Address: -
      Source Port: -

      Detailed Authentication Information:
      Logon Process: Advapi
      Authentication Package: Negotiate
      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="http://schemas.microsoft.com/win/2004/08/events/event">
        <System>
        <Provider Name="Microsoft-Windows-Security-Auditing" Guid=" {54849625-5478-4994-A5BA-3E3B0328C30D}

        " />
        <EventID>4625</EventID>
        <Version>0</Version>
        <Level>0</Level>
        <Task>12544</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8010000000000000</Keywords>
        <TimeCreated SystemTime="2016-07-08T22:26:11.765645000Z" />
        <EventRecordID>1682</EventRecordID>
        <Correlation />
        <Execution ProcessID="468" ThreadID="532" />
        <Channel>Security</Channel>
        <Computer>pe-201612-agent-win2008</Computer>
        <Security />
        </System>
        <EventData>
        <Data Name="SubjectUserSid">S-1-5-21-1860036329-3057280495-287023118-500</Data>
        <Data Name="SubjectUserName">vagrant</Data>
        <Data Name="SubjectDomainName">PE-201612-AGENT</Data>
        <Data Name="SubjectLogonId">0xf07a</Data>
        <Data Name="TargetUserSid">S-1-0-0</Data>
        <Data Name="TargetUserName">vagrant</Data>
        <Data Name="TargetDomainName">PE-201612-AGENT</Data>
        <Data Name="Status">0xc000006d</Data>
        <Data Name="FailureReason">%%2313</Data>
        <Data Name="SubStatus">0xc000006a</Data>
        <Data Name="LogonType">3</Data>
        <Data Name="LogonProcessName">Advapi </Data>
        <Data Name="AuthenticationPackageName">Negotiate</Data>
        <Data Name="WorkstationName">PE-201612-AGENT</Data>
        <Data Name="TransmittedServices">-</Data>
        <Data Name="LmPackageName">-</Data>
        <Data Name="KeyLength">0</Data>
        <Data Name="ProcessId">0x538</Data>
        <Data Name="ProcessName">C:\Program Files\Puppet Labs\Puppet\sys\ruby\bin\ruby.exe</Data>
        <Data Name="IpAddress">-</Data>
        <Data Name="IpPort">-</Data>
        </EventData>
        </Event>

      This can result in inadvertent user lockouts.

        Attachments

        1. puppet_apply_2-security_log-x64.png
          61 kB
          Rob Reynolds
        2. puppet_apply_2-x64.png
          7 kB
          Rob Reynolds
        3. puppet_apply-security_log-x64.png
          110 kB
          Rob Reynolds
        4. puppet_apply-x64.png
          20 kB
          Rob Reynolds
        5. puppet_resource_user-security-log-x64.png
          15 kB
          Rob Reynolds
        6. puppet_resource_user-x64.png
          26 kB
          Rob Reynolds

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  rob Rob Reynolds
                  Reporter:
                  erik.hansen Erik Hansen
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Due:
                    Created:
                    Updated:
                    Resolved: