New answers tagged


I've ended up at exactly the same spot. We have a Vault server holding a good deal of secrets for different environments and various endpoints for each environment, so we set up kv engines for every environment and added a descriptive path for every secret. For instance, we have called our engines constant-text/environment/engine-name and all Database users ...


Yes, it's possible as following: vault read -format=json auth/jwt/role/ROLENAME

Top 50 recent answers are included