Jira (PUP-1210) authentication_authority key is not set when managing root's password using the puppet user provider

[Nate Walck (JIRA)]

Title: Message Title

Nate Walck commented on an issue   Re: authentication_authority key is not set when managing root's password using the puppet user provider Andy Parker, I think the provider should outright fail if Iterations or salt are missing on a 10.8+ machine. Obviously you cannot predict a bad iterations value, but if one of the two is missing it should behave as if you are missing a required parameter (because you are). If you try to manage the root user exactly as you would a regular user, you cannot log in via the GUI, which is the issue that this bug is referencing. Something different happens with the root user to enable it that is not required for non-root users. Perhaps this functionality isn't even necessary as using root is bad practice, but it was a noted bug that gave no indication that it hadn't actually worked. Add Comment   Puppet / PUP-1210 authentication_authority key is not set when managing root's password using the puppet user provider If you try to set the root password on OS X using the Puppet user provider, there are two bugs: 1. /var/db/dslocal/nodes/Default/users/root.plist has the 'passwd' key set incorrectly. It sets: {code:xml} <key>passwd</key> <string>********</string> {code} when it should be: {code:xml} <key>passwd</key> <array>              <string>******... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.