Bug #12191
Unable to remotely sign a SSL certificate via certificate face
| Status: | Merged - Pending Release | Start date: | 01/26/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Faces | |||
| Target version: | 3.0.0 | |||
| Affected Puppet version: | 2.7.10 | Branch: | https://github.com/puppetlabs/puppet/pull/410 | |
| Keywords: | ||||
| Votes: | 0 |
Description
It is currently not possible to sign a certificate remotely using the certificate face. This is due to the fact that options[:ca_location] is a string and not a symbol.
I have submitted pull request #410 (https://github.com/puppetlabs/puppet/pull/410) to resolv the problem.
Related issues
History
Updated by James Turnbull 4 months ago
- Status changed from Unreviewed to In Topic Branch Pending Review
- Branch set to https://github.com/puppetlabs/puppet/pull/410
Updated by Daniel Pittman 4 months ago
- Status changed from In Topic Branch Pending Review to Merged - Pending Release
- Target version set to 2.7.11
Updated by Daniel Pittman about 1 month ago
- Target version changed from 2.7.11 to 3.X
This was actually merged to trunk, not the 2.7 stable branch. If folks can test it on 2.7 and it solves a real problem we can revisit getting it into stable.
Updated by Kristof Willaert about 1 month ago
It does solve the remote signing of certs problem I was having with 2.7.12.
Without it, I get this:
$ puppet certificate generate testnode.lan --ca-location remote true $ puppet certificate sign testnode.lan --ca-location remote err: This process is not configured as a certificate authority err: Try 'puppet help certificate sign' for usage
With the fix applied, the signing works:
$ puppet certificate sign testnode.lan --ca-location remote "-----BEGIN CERTIFICATE-----\nMCUwGwIAMAMGAQAwADAEHwAfADAAMAgwAwYBAAMBADADBgEAAwEA\n-----END CERTIFICATE-----\n"
Updated by Daniel Pittman 7 days ago
- Target version changed from 3.X to 3.0.0