Issue #7243 has been updated by James Turnbull.
Matt X509 Attributes are made up of OIDs (like SNMP) and values. The OIDs in the file are converted to their named values - in this case testoid1 and testoid2. How do you intend to get the values from the CSR to validate them? ---------------------------------------- Feature #7243: Additional data in Puppet CSRs (certdnsnames, and custom data) https://projects.puppetlabs.com/issues/7243 Author: Matt Wise Status: Needs More Information Priority: Normal Assignee: Matt Wise Category: SSL Target version: Telly Affected Puppet version: Keywords: Branch: https://github.com/jamtur01/puppet/tree/tickets/master/7243 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.
