Issue #7243 has been updated by Adrien Thebo.
Hi Patrick, Would you be able to file a pull request against the Github repo (https://github.com/puppetlabs/puppet) ? This well help us start reviewing the code on a more formal level. You might want to review https://github.com/puppetlabs/puppet/blob/master/CONTRIBUTING.md to see what we need when merging code into Puppet. ---------------------------------------- Feature #7243: Additional data in Puppet CSRs (certdnsnames, and custom data) https://projects.puppetlabs.com/issues/7243#change-83701 Author: Matt Wise Status: Tests Insufficient Priority: Normal Assignee: Daniel Pittman Category: SSL Target version: Affected Puppet version: Keywords: Branch: https://github.com/puppetlabs/puppet/pull/806 Puppet Clients currently do not support filling in 'certdnsnames' in their CSR. That is only done on the signing-server side of things. This should be updated so that either the client, or server can set the certdnsnames (or both). In addition to this, the Puppet CSR generation code should allow for the addition of arbitrary data in the form of keypairs (foo=xyz) that is embedded into the CSR. That data should then be accessible in some way to the Puppet master process itself during catalog compilation. This allows for companies to build in their own security models around the SSL certs. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
