Searching for a secret returns 404 Not Found when the Vault path contains a colon (:)

[yakovkrainov]

When a Vault secret path contains a colon (:), the extension returns 404 Not Found.

Vault expects colons (and other path characters) to remain literal in secret paths. The extension URL-encodes the path, so it no longer matches the existing secret.

Rendered error:

getCredentials: function text() { [native code] }

Unsafe workaround:

popup.js, around line 93

- const url = vaultAddr + "/v1/" + encodeURIComponent(path);
+ const url = vaultAddr + "/v1/" + encodeURI(path);

Common case:

Services differentiated by custom ports