@@ -92,10 +92,8 @@ filters you have two options:
9292
9393#### Issue
9494
95- Users cannot list KV v2 secrets in the GUI if their policy grants ` list ` access to metadata
96- but the policy path does not include a trailing slash.
97-
98- Example of a policy that previously granted users list access and now returns an error:
95+ Users cannot list KV v2 secrets in the GUI when the policy granting ` list `
96+ access to metadata does not include a trailing slash. For example:
9997
10098```
10199path "secret/metadata/:path" {
@@ -105,21 +103,23 @@ path "secret/metadata/:path" {
105103
106104#### Workaround
107105
108- To resolve the policy issue, add a trailing slash to the policy path until the fix is released:
106+ Option 1: Use the API explorer to list KV v2 secrets instead of the KV v2 GUI page:
107+
108+ 1 . Select ** Tools** from the Vault GUI sidebar.
109+ 1 . Click ** API Explorer** .
110+ 1 . Enter the KV v2 plugin mount path in the "Filter by tag" search bar.
111+ 1 . Expand the ` GET /:mount/metadata/{path}/ ` endpoint and click ** Try it out** .
112+ 1 . Input the secret ` path ` click ** Execute** to perform the HTTP request.
113+
114+ Option 2: Add a trailing slash to the policy path:
109115
110116```
111117path "secret/metadata/:path/" {
112118 capabilities = ["list"]
113119}
114120```
115121
116- You can also use the API explorer to list KV v2 secrets:
117122
118- 1 . Select ** Tools** from the Vault GUI sidebar.
119- 1 . Click ** API Explorer** .
120- 1 . Enter the KV v2 plugin mount path in the "Filter by tag" search bar.
121- 1 . Expand the ` GET /:mount/metadata/{path}/ ` endpoint and click ** Try it out** .
122- 1 . Input the secret ` path ` click ** Execute** to perform the HTTP request.
123123
124124### GUI KV v2 listing secrets fails in namespaces ((#gui-kvv2-list-namespaces)) <EnterpriseAlert inline = " true" />
125125
@@ -129,12 +129,12 @@ You can also use the API explorer to list KV v2 secrets:
129129
130130#### Issue
131131
132- The GUI displays a "No secrets yet" message for KV v2 engines with existing secrets when
133- users navigate to the list secrets in a namespace.
132+ The GUI displays "No secrets yet" message for KV v2 engines with existing secrets when
133+ users navigate to the plugins secret list in a namespace.
134134
135135#### Workaround
136136
137- You can use the web REPL to list KV v2 secrets:
137+ Use the CLI emulator to list KV v2 secrets:
138138
1391391 . Navigate to the desired namespace.
1401401 . Toggle open the web REPL.
0 commit comments