Open gioppoluca opened 6 months ago
Calling a curl on this URL: Using root token to be sure
https://vault.mysite_redacted/v1/kv-v2/metadata/my/path/to/svil/my_secret?list=true
In this path with the UI I can see that there is a key called "password" Describe the bug get a 404 not found
To Reproduce
Expected behavior expect to see something like this:
{ "request_id": "5e61e30f-8bfe-54cb-8627-80c84aab232c", "lease_id": "", "renewable": false, "lease_duration": 0, "data": { "keys": [ "password" ] }, "wrap_info": null, "warnings": null, "auth": null }
Environment:
vault status
vault version
Vault server configuration file(s):
Additional context Using root token to be sure not having permission problems as a test; not even with root token the curl works
same if I execute: vault kv list kv-v2/my/path/to/svil/my_secret result is: No value found at kv-v2/metadata/my/path/to/svil/my_secret
vault kv list kv-v2/my/path/to/svil/my_secret
No value found at kv-v2/metadata/my/path/to/svil/my_secret
Keys are there and shown in the UI only the API is refusing to show them
Calling a curl on this URL: Using root token to be sure
https://vault.mysite_redacted/v1/kv-v2/metadata/my/path/to/svil/my_secret?list=true
In this path with the UI I can see that there is a key called "password" Describe the bug get a 404 not found
To Reproduce
Expected behavior expect to see something like this:
Environment:
vault status
): 1.12vault version
): using CURLVault server configuration file(s):
Additional context Using root token to be sure not having permission problems as a test; not even with root token the curl works