IssueRaiser

List all secret paths a user has permission to view

**Is your feature request related to a problem? Please describe.** Currently, for our users to be able to navigate the vault GUI, we need to apply `path "secret/*" { capabilities = ["list"] }` to that user. Without it, they receive an error after they click into the secret engine (see pic). However, when we grant that permission, the user can then list ALL secrets. From a user stand point, this is confusing because they can list every secret in our vault but cannot access the actual secret. ![vault_secret_list_error](https://user-images.githubusercontent.com/3812162/45776891-4a85e900-bc22-11e8-93f4-729387b3613d.jpg) **Describe the solution you'd like** it would be great for our users to be able to list (view in the gui) only secret paths that they have access to and not see secret paths if they dont have access. **Describe alternatives you've considered** Cant think of any.. probably the current solution is the only other alternative: grant secret/* list **Explain any additional use-cases** We're using 0.11 enterprise preimum + hsm with a kv2 secret engine. The guide ive been following is: https://www.vaultproject.io/docs/secrets/kv/kv-v2.html#acl-rules and https://support.hashicorp.com/hc/en-us/articles/360000953148-Vault-UI-Secrets-Navigation In the example below, ive also tried in the CLI with the same results: 1. the policy we've applied to the user Taf policy ``` path "secret/metadata/taf/*" { capabilities = ["list", "read"] } path "secret/data/taf/*" { capab

Posted by drewmullen on Sep 19, 2018, 7:15 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments

ux (Other)

List all secret paths a user has permission to view

drewmullenSep 19, 2018, 7:15 PM

**Is your feature request related to a problem? Please describe.** Currently, for our users to be able to navigate the vault GUI, we need to apply `path "secret/*" { capabilities = ["list"] }` to that user. Without it, they receive an error after they click into the secret engine (see pic). However, when we grant that permission, the user can then list ALL secrets. From a user stand point, this is confusing because they can list every secret in our vault but cannot access the actual secret. ![vault_secret_list_error](https://user-images.githubusercontent.com/3812162/45776891-4a85e900-bc22-11e8-93f4-729387b3613d.jpg) **Describe the solution you'd like** it would be great for our users to be able to list (view in the gui) only secret paths that they have access to and not see secret paths if they dont have access. **Describe alternatives you've considered** Cant think of any.. probably the current solution is the only other alternative: grant secret/* list **Explain any additional use-cases** We're using 0.11 enterprise preimum + hsm with a kv2 secret engine. The guide ive been following is: https://www.vaultproject.io/docs/secrets/kv/kv-v2.html#acl-rules and https://support.hashicorp.com/hc/en-us/articles/360000953148-Vault-UI-Secrets-Navigation In the example below, ive also tried in the CLI with the same results: 1. the policy we've applied to the user Taf policy ``` path "secret/metadata/taf/*" { capabilities = ["list", "read"] } path "secret/data/taf/*" { capab

Comments (0)

No comments yet. Start the discussion.

Comment on this issue