Hi Matt,
I've not tried it myself, but
https://puppet.com/docs/puppetserver/5.3/config_file_auth.html#hocon-example
with a `match-request` selecting the hostname and a backreference in the
`allow` section seems the new way to do this.
Cheers, David
On Thu, Nov 15, 2018 at 9:44 PM Matt Zagrabeln
Apologies for the late reply but do you know how to re-create the certs for
PuppetDB ? Is there a specific PuppetDB group who may be able to answer
this ? Thanks very much.
On Wednesday, 3 October 2018 19:04:26 UTC+1, Maggie Dreyer wrote:
>
> If you regenerated your CA as part of fixing the issu
Hmm perhaps I should RTFM :
https://puppet.com/docs/puppetdb/6.0/maintain_and_tune.html#redo-ssl-setup-after-changing-certificates
On Friday, 16 November 2018 16:49:20 UTC, Andy Hall wrote:
>
> Apologies for the late reply but do you know how to re-create the certs
> for PuppetDB ? Is there a sp
Greetings!
We're happy to announce the release of Bolt 1.3.0. Highlights in this
release include:
- Running commands on containers
- Waiting until target nodes accept connections
For more information, check out the release notes:
https://puppet.com/docs/bolt/1.x/bolt_release_notes.html
To
Hello Morgan
I was able to generate a new certificate with the alt name, and when doing
a 'puppet cert list --all' I see the following:
+ "puppet4.psd401.net" (SHA256) 1D:16:67:30:0D:62:CE:6C:2A:80:11:7E:C7:79:BA
:4F:25:C6:0E:E6:90:9D:4D:9F:86:4B:5C:42:A1:6D:09:96 (alt names: "DNS:puppet"
, "DN
