[PUP-3178] puppet certificate generate also generate certs/key that match the FQDN Created: 2014/09/03  Updated: 2016/06/18  Resolved: 2016/06/18

Status: Closed
Project: Puppet
Component/s: None
Affects Version/s: PUP 3.6.2
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Laurent Bigonville Assignee: Unassigned
Resolution: Duplicate Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

SLES11


Issue Links:
Duplicate
duplicates PUP-2018 `puppet certificate generate` Generat... Closed
Template:

 Description   

Hi,

When running the following command, puppet certificate also generate and seems to send a CSR to the puppet master for a key that matches the FQDN in addition to the one requested.

puppet certificate generate jenkins-example-com --ssldir ~/.mcollective.d/credentials --ca-location remote --ca_server puppet.example.com

This is causing issue if you already have your machine signed by the puppet master. This didn't seem to be the case with puppet 2.7.3



 Comments   
Comment by Mathew Archibald [ 2015/07/13 ]

I'm also experiencing this issue and it is stopping me being able to register new mcollective user certificates from the example http://docs.puppetlabs.com/mcollective/deploy/standard.html#managing-client-credentials

Puppet Version 3.4.3

Comment by Josh Cooper [ 2016/06/18 ]

This looks to be a dup of PUP-2018, marking this as such.

Generated at Fri Jan 17 19:41:38 PST 2020 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.