This message was deleted.
# puppet-enterprise
s
This message was deleted.
b
hi o/
used that a few months ago and worked fine
z
👋 Thank you!
b
also the maintainer worked for puppet and then hashicorp, so if you have some trouble Peter csn usually quickly help out
z
Great! Thanks so much for the info
I might be curious if this supports certificate-based auth rather than using a token. E.g. if the client/server is signed with the Puppet CA, allow access to vault
b
I think the recommendation is to run vault agent on the puppetserver. puppetsetver/hiera can authenticate with a token to vault agent and the agent uses cert or approle authentication to the vault cluster
and the cert auth can use puppet CA
c
We've had a recent report of Vault not being able to properly validate certificates issued by the Puppet 6 CA.
If I recall correctly, the Puppet Root CA having a serial number of 1 and the Puppet sub-CA also having a serial number of 1 confuses Vault TLS validation --- it doesn't recognize those numbers are in separate "namespaces".
b
well theres an old feature request to switch to UIDs as serials :D
that would be nice <3
c
Yeah, they looked into it for Puppet 8, but the switch isn't straight-forward due to Java not having a 128 bit integer type: https://tickets.puppetlabs.com/browse/SERVER-2640
b
yeah :(
would really be nice to have that for active/active CAs
c
It would enable active/active issuing of certs. Revocation is still tricky.
b
yep
z
Curious if this poses a risk to have a long-lived token, given that it has to be manually specified in the hiera config
too bad that Puppet cant fetch a new token over time before ttl has expired
b
I think I used a path to a tokenfile
but I dont remember how the renewal worked :D
z
right, but that's still long-lived, correct?
I will definitely use a file.
b
I am not sure
I think it can do some auto token refresh?
a good question for Peter :D
maybe raise a github issue with ,"how to use this in a secure way"
m
If anyone tries using the cert auth and sees it work, I'd love to hear it. We have some internal testing that does it successfully...
b
I need to spin a vault stack up for some PE customers soon, I will update you. It worked fine the last time
@csharpsteen do you know if theres a bugreport somewhere about vault nit liking the PuppetCA chain?
I would like to know if this is a regresssion
m
As far as I know no bug ticket has been filed (I've been working with the customer in question), but I was also brought into the convo kinda late
b
ah okay
m
A lot of their other related complaints were more "this seems bad" than "this is actually broken" so I'm not totally sure what to make of the report
The docs in question I found that refer to the issue are here https://developer.hashicorp.com/vault/docs/auth/cert There's a note in there about unique serials
b
ah the usual customer reports :D
as a workaround recreating the intermediate cert should be quite easy 🤔
m
Yeah for sure, if you were willing to redistribute the new certs across your fleet.
The UUID thing is unfortunately quite complicated and touches a lot of components, even though that does feel like the "right" way to solve this (and many other) problems
b
I already feared that :(