-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Per-client cert policies possible? #46
Comments
Hi, you can have one dynamic policy using the Template variables But you cannot add different policy, hope it helps |
Thanks, I was hoping not to make the path itself host specific. An example would be 'host1' and 'host2' have access to Anything come to mind as to this being possible? If not, I'll have to go down a different road. |
Vault 1.10 merges in PR#13348 which will populate the entity alias metadata hash with the cert extensions of the client cert. So using cert extensions when you sign your agent cert, you should be able to set arbitrary values that you can use in vault to template with. Though full disclosure, I haven't tried this yet since my vault instance isn't at 1.10 yet. |
I think this is possible you need access to write to the cert authenticator in vault you can then upload puppet's CA cert multiple times associating it with different policies and different sets of common names. those policies then restrict you to a particular kv path so if you had alice_secrets and a policy puppetcert_alice_secret_access you then upload the puppet CA cert with vault like this:
|
I've set this module up and it seems to work as far as allowing all Puppet agents to use the same policy by setting it at the
auth/cert/certs/puppetserver
as documented.Is it possible with this method to give specific agents specific policies? If so, some documentation would be appreciated.
The text was updated successfully, but these errors were encountered: