You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
create a large number of secrets in folders. (/secret/users-space/idxxxx/dev/....)
try go to second page
Type kv
Path secret/
Local No
Seal wrap No
Version. 1
Environment:
Vault Server Version (retrieve with vault status):
* / $ vault status
Key Value
--- -----
Seal Type awskms
Recovery Seal Type shamir
Initialized true
Sealed false
Total Recovery Shares 5
Threshold 3
Version 1.17.2
Build Date 2024-07-05T15:19:12Z
Storage Type raft
Cluster Name xxxxxxxxx
Cluster ID xxxxxxx
HA Enabled true
HA Cluster https://vault-2.vault-internal:8201
HA Mode standby
Active Node Address https://10.12.135.165:8200
Raft Committed Index 4197955693
Raft Applied Index 4197955692
Vault CLI Version (retrieve with vault version): * Vault v1.17.2 (2af5655e364f697a15b1dc2db2c3f85f6ef949f2), built 2024-07-05T15:19:12Z
Server Operating System/Architecture:
aws eks 1.28 bottle rocket amd64
Vault server configuration file(s):
helm chart in k8s.
i think conf not need.
The text was updated successfully, but these errors were encountered:
Describe the bug
A clear and concise description of what the bug is.
i go to the https://vault.dev/ui/vault/secrets/secret/list/user-space/
and link to next page is
https://vault.dev/ui/vault/secrets/secret/list/secret?page=2
i get 404 because has no such folder(path)
i expect
https://vault.dev/ui/vault/secrets/secret/list/user-space/?page=2. (this work if type manually)
look like
https://vault.dev/ui/vault/secrets/(kv engine name)/list/(kv engine name)?page=2
but need something like
https://vault.dev/ui/vault/secrets/(kv engine name)/list/(secret path)?page=2
To Reproduce
Steps to reproduce the behavior:
Environment:
vault status
):vault version
):* Vault v1.17.2 (2af5655e364f697a15b1dc2db2c3f85f6ef949f2), built 2024-07-05T15:19:12Z
Vault server configuration file(s):
The text was updated successfully, but these errors were encountered: