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.  **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
- To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
- > The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
- Custom trigger IDs are not displayed in the new 2026.10 trigger selector
- I hate that too, but I think it’s more the ux than the concept of a default.
- > The biggest problem with UX developers is they know better than you AND force you into their paradigm.
- "Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments
ux (Other)
To be fair, Inform7 can't succeed, generally, because there is no market for the kind of games that you create with Inform7.
> The notion that somehow LR reliability is misunderstood by Consumer Reports, JD Power, Car & Driver, Automobile etc.
Custom trigger IDs are not displayed in the new 2026.10 trigger selector
I hate that too, but I think it’s more the ux than the concept of a default.
> The biggest problem with UX developers is they know better than you AND force you into their paradigm.
"Focus follows mouse" is what I use to keep the file manager from popping up when click-dragging files.
The biggest problem with this is if the target URL doesn't load but also doesn't quickly error out, like e.g.
Google wants to build up a private web here.
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.  **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.