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

dynamic secrets for access to Vault? #288

Closed
chadwhitacre opened this issue May 31, 2015 · 7 comments
Closed

dynamic secrets for access to Vault? #288

chadwhitacre opened this issue May 31, 2015 · 7 comments

Comments

@chadwhitacre
Copy link
Contributor

I want to give people access to a web app (at Heroku, as it happens) that has access to Vault, without giving the people the same access to Vault as the web app has. This could be achieved with a vault secret backend that supported dynamic secrets, yes?

@chadwhitacre
Copy link
Contributor Author

Custom Secret Backends

Vault doesn't currently support the creation of custom secret backends. The primary reason is because we want to ensure the core of Vault is secure before attempting any sort of plug-in system. We're interested in supporting custom secret backends, but don't yet have a clear strategy or timeline to do.

http://vaultproject.io/docs/secrets/custom.html

@sethvargo
Copy link
Contributor

Hi @whit537

From the description of the issue (and please correct me if I am wrong), you are trying to use Vault as an authentication system. Vault is not really designed for this use case.

@chadwhitacre
Copy link
Contributor Author

@sethvargo Actually, I'm trying to use Vault as a PCI vault (gratipay/gratipay.com#3504), and I'm trying to avoid dragging the entire web app into compliance scope. How can I keep my vault segmented from a PCI perspective, even if someone compromises the web app?

P.S. Hi! 👋 :)

@chadwhitacre
Copy link
Contributor Author

To be honest, though, I might be able to solve my problem with ACLs that only allow writing from the web app for the cases I care about.

I still think this could be a neat idea, though, even if I don't need it right now. My understanding of dynamic secrets was that they allowed one to generate credentials on the fly for a system like AWS or Postgres. The thought was: What about generating credentials on the fly for Vault? That might require a two-vault setup, dunno.

Anyway, feel free to close if you're not interested. I think for my immediate use-case I will explore the ACL option.

@armon
Copy link
Member

armon commented Jun 1, 2015

@whit537 This is possible! The token auth mechanism at the heart of Vault supports this notion of sub-tokens. See both: https://vaultproject.io/docs/internals/token.html and https://vaultproject.io/docs/auth/token.html

@jefferai
Copy link
Member

Also, in Vault 0.5 you can specify write-only ACLs, which should fit your needs nicely.

@chadwhitacre
Copy link
Contributor Author

Thanks! :-)

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

No branches or pull requests

4 participants