Vault User Research: Why do you think some people get stuck? (short survey)

Hello from Vault’s User Research team!

Our team has been debating what to build to help more people get started with Vault. While we have data on downloads, we’re curious about …

  • Who you are as a human being,

  • What programming languages you’re fluent in, and

  • How much time you expected (or expect) to spend getting Vault to consume a secret for the first time?

  • Why do you think some people get stuck on their way to their first secret?

Would you take ~3 minutes to complete this hopefully fun survey?

~Chrissie, HashiCorp UXR

1 Like

Done. That was a very funny one. :grin:

1 Like

Didn’t find questions in the survey WHY someone get stuck. I’m stuck with policies infinitely googling for simple questions. There’s even no answer in the documentation “whether a wildcard matches subdirectories”? (will foo/* match foo/bar/baz?)

Why all demos/samples in the internet shows paths like foo/bar but in my case they always prefixed with kv/. Should I add this prefix always or can go without it? Are these samples from the real live? Why my paths are prefixed? Why I can not have a path without the prefix? When I read official doc I see kv put - Command | Vault by HashiCorp

vault kv put secret/creds passcode=my-long-passcode

And when I run it I get

Error making API request.

URL: GET https://***
Code: 403. Errors:

* preflight capability check returned 403, please ensure client's policies grant access to path "secret/creds/"

WTF??? Using the cloud vault brought only a lot of frustration.

I seems I will spend my $50 credit just for getting very basics of using vault instead of real life usage because of no consistent documentation for it…

1 Like

One more point to frustrate: How to enable audit logs in vault cloud? (documentation says there should be a button to access logs, but in the reality, no such button).