Jira (PUP-5224) the no-client option has been removed, preventing key creation
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5224 the no-client option has been removed, preventing key creation Change By: Josh Cooper Affects Version/s: PUP 4.2.2 Affects Version/s: PUP 4.2.1 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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.
Jira (PUP-5224) the no-client option has been removed, preventing key creation
Title: Message Title Jo Rhett created an issue Puppet / PUP-5224 the no-client option has been removed, preventing key creation Issue Type: Bug Affects Versions: PUP 4.2.2 Assignee: Unassigned Created: 2015/09/11 4:34 AM Priority: Normal Reporter: Jo Rhett There are numerous reasons to acquire a key from a Puppet server, including 1. To create a code deployment key for invalidating the environment cache 2. To create per-user keys used for MCollective authentication ...etc. Manually generating the key on the server and then copying the private key across the network to the node is not ideal for many reasons. In some situations the client would rather not have someone else possess their private key for any reason. The connect/authorize model works very well for this. The old process was: $ puppet agent --certname code-deployment --no-client --test
