From the course: Learning HashiCorp Vault

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Working with Vault secrets engines

Working with Vault secrets engines - Vault Tutorial

From the course: Learning HashiCorp Vault

Start my 1-month free trial

Working with Vault secrets engines

- [Instructor] Let's take a look at the secrets engines that are enabled by default in a new vault server. If you don't have a vault dev server running, open a new terminal and execute vault server dash dev. You'll then need to open a second terminal window and execute these commands. Export vault underscore addr equals quote http colon slash slash 127.0.1 colon 8200 close quote. Once again, if you wanna that this permanently, you can look for instructions on how to set a permanent environment variable for your platform. Now you can execute vault secrets list. This command lists all of the enabled secrets engines. The cubbyhole secrets engine is a variant of the KV secrets engine. Cubbyhole access is scoped by token, which means that a cubbyhole token can only read one cubbyhole, and each cubbyhole has only one valid token. When a cubbyhole token expires, the cubbyhole is destroyed. We'll see the cubbyhole in use when we use vault to inject secrets into an application on deployment…

Contents