EDIT I would recommend viewing roles through the CLI. Viewing roles through the UI seems show all roles instead of those assigned to a given auth method. Viewing roles using the UI Click the “Access” tab Click “View Configuration” under the three dot dropdown for the auth method you’re interested in Click the “Roles” tab … Read more
This is my current docker-compose config for using Vault in dev, but I use dedicated servers (not Docker) in production. # docker_compose.yml version: ‘2’ services: myvault: image: vault container_name: myvault ports: – “127.0.0.1:8200:8200” volumes: – ./file:/vault/file:rw – ./config:/vault/config:rw cap_add: – IPC_LOCK entrypoint: vault server -config=/vault/config/vault.json The volume mounts ensure the vault config is saved if … Read more
This was a result of me not reading documentation. The request was failing because there was no secret engine mounted at that path. You can check your secret engine paths by running vault secrets list -detailed This showed that my kv secret engine was mapped to path kv not secret as I was trying. Therefore … Read more
I fixed the problem. Though the exception can be common to more than one similar problem, I fixed the problem by exporting the root token generated after running this command : vault server -dev The output is like this … You may need to set the following environment variable: $ export VAULT_ADDR=’http://127.0.0.1:8200′ The unseal key … Read more