Issue #1891 has been updated by Matt Wise.
My bug (7244) is essentially a more open version of whats described here. Rather than explicitly having Puppet handle the 'token' or 'auth code' part of it, it just passes that to an external script that validates the data and tells puppet whether or not its been accepted. This allows for each environment to define their own key system however they wish. You could even pass an LDAP login name and password and have the script validate that against some LDAP server, if that was how your environment worked (im not suggesting that!). ---------------------------------------- Feature #1891: Auto-sign certificates if sent the correct passphrase with the certificate request https://projects.puppetlabs.com/issues/1891 Author: Hari Sekhon Status: Accepted Priority: Normal Assignee: Category: SSL Target version: unplanned Affected Puppet version: 0.24.6 Keywords: Branch: Setting an auto-sign passphrase on the puppet CA would allow a completely automated build of a new system that has the passphrase embedded in the installation script. The request should be able to take the passphrase on the command line via a switch. This offers the best of all worlds, security in not auto-signing just anything, but still having ease of use, speed and automation of deployments of new systems since you'd no longer need to go to the puppetmaster's CA and manually type in to accept pending certificates. -- 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.
