Issue #7243 has been updated by James Turnbull. Status changed from Code Insufficient to In Topic Branch Pending Review Branch changed from https://github.com/jamtur01/puppet_old/tree/tickets/master/7243 to https://github.com/puppetlabs/puppet/pull/269
I've updated this code since the Code Orange changes. It still needs tests for which I will need help. But it's a long-standing requirement for several large customers and I'd like to get this on the radar. Or if someone can suggest a better implementation I am also open to that! :) ---------------------------------------- Feature #7243: Additional data in Puppet CSRs (certdnsnames, and custom data) https://projects.puppetlabs.com/issues/7243 Author: Matt Wise Status: In Topic Branch Pending Review Priority: Normal Assignee: Daniel Pittman Category: SSL Target version: 2.7.x Affected Puppet version: Keywords: Branch: https://github.com/puppetlabs/puppet/pull/269 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 post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
