Skip to content
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

Support for hashicorp vault #2128

Open
shivabasu opened this issue May 19, 2022 · 5 comments
Open

Support for hashicorp vault #2128

shivabasu opened this issue May 19, 2022 · 5 comments

Comments

@shivabasu
Copy link

Support hashicorp vault vault to store DNS Auth keys. So that DNS keys are encrypted and kept and end-users will not have access to them.

@WouterTinus
Copy link
Member

It'd be useful to have some more input from the community about this possible enhancement. Like which authentication method(s) you'd prefer to connect to the Vault and whether you use the Vault Agent or not.

@shivabasu
Copy link
Author

In the Intranet use case, we need auto-renewal functionality with the DNS validation method. Due to security reasons, we can't share google DNS service account with our end users.
( --validation gcpdns --serviceaccountkey xxx --projectid xxx ).

Instead of this we would like to integrate with hashicorp vault to store Google DNS Service key or

Vault static secrets will be preferred
https://learn.hashicorp.com/tutorials/vault/static-secrets

@WouterTinus
Copy link
Member

Possible library to use for this: https://github.com/rajanadar/VaultSharp

@webprofusion-chrisc
Copy link
Contributor

Their http API is quite useful if you don't want to take a dependency on a library, I've only used it for storing certs

https://github.com/webprofusion/certify-plugins/blob/development/src/DeploymentTasks/Core/Providers/HashicorpVault.cs

@WouterTinus
Copy link
Member

The next release will make it possible to load external plugins for the secret vault in the same way that you can now load plugins for different stages of the certificate renewal process. But since I don't have access to or experience with any Hashicorp product, someone else would have to implement the interface in a seperate project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants