-
Notifications
You must be signed in to change notification settings - Fork 22
not able to view all secrets #20
Comments
I'm assuming this is because you have another backend(s) mounted at another location other than "secret", which this currently specifically keys too. See: This could be probably be fixed by querying for a list of secret backends first, then running that method for each. |
This should be fixed with pull request #23 |
@jasonmcintosh im not sure this will fix the issue. The problem is as @nyxcharon described above. there are multiple secret backends, these would need to be looped through, or have the ability to select a mounted backend to browse. |
Whoops mis-read this... yeah need to loop over the secret backends to do this. |
+1 for this. We have multiple "namespaces" and each user is only allowed to access their specific namespace with their specific ACLs. I have to do something like this to access my secrets:
$company is always the same. Or I guess you could call "$company/$team" the "namespace". |
I have an initial fix on the secret-view branch, and I'd like some testing from others if possible. I went ahead and built a docker container for it as well - nyxcharon/vault-ui:secret-view @warroyo @rlueckl can you guys test please? I tested with two secret backends mounted, but I might be missing a use case. |
Hi, I did a quick test, unfortunately I don't see the secrets. Started with Then I logged in with my credentials. All pages (Secrets, Mounts, Users, Policies) are completely empty. :( I don't see any errors or debug output, so this is all I've got. |
I am able to see secrets from one of my generic backends, however it seems to be limiting the number of paths displayed. it also is not displaying any of the other backends secrets. |
I have a user with the "root" policy however i am only able to see one of my generic secret backends secrets. I am able to see all mounts and users, etc. however when i try to view secrets it only lists one of the backends secrets. is there a way to switch backends? when making rest calls directly from postman i am able to see the missing secrets
The text was updated successfully, but these errors were encountered: