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

Windows - Group resource member parameter outputs an array of SID's instead of Names

    Details

    • Template:
      PUP Bug Template
    • Team:
      Platform OS
    • Sprint:
      Platform OS Kanban
    • Method Found:
      Needs Assessment
    • CS Priority:
      Reviewed
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      The Windows group provider now properly prints the members as <DOMAIN>/<user> in puppet resource's output.
    • QA Risk Assessment:
      Needs Assessment

      Description

      Puppet Version: 5.5.8 (PE 2018.1.5)
      Puppet Server Version: 5.3.6
      OS Name/Version: Windows 2019

      This ticket has arisen from a support case where the customer had noticed that a custom fact of theirs that used the group resource parameter member no longer worked after upgrading from PE 2018.1.3 to 2018.1.5.

      After a quick repro and speaking with some of the devs, this looks like a regression issue. In 2018.1.3, member outputs names and in 2018.1.5 SID's were outputted:

      2018.1.3 (Puppet 5.5.3) Group resource:

      group { 'Users':
        ensure  => 'present',
        gid     => 'S-1-5-32-545',
        members => ['NT AUTHORITY\INTERACTIVE', 'NT AUTHORITY\Authenticated Users', 'PL2U24SBREN5JPS\sshd', 'PL2U24SBREN5JPS\cyg_server'],
      

      2018.1.5 (Puppet 5.5.8) Group resource:

      group { 'Users':
        ensure  => 'present',
        gid     => 'S-1-5-32-545',
        members => ['S-1-5-4', 'S-1-5-11', 'S-1-5-21-1925060020-2411252292-4197056437-1000', 'S-1-5-21-1925060020-2411252292-4197056437-1001'],
      

      Desired Behavior: Output of the Group Member parameter should be an array of Names and not SIDs.

      Actual Behavior: Currently an array of SID's is outputted

        Attachments

          Activity

            People

            • Assignee:
              enis.inan Enis Inan
              Reporter:
              patrick.grant Patrick Grant
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support