Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

-s in secrets engine makes them unreadable #240

Open
mike-bailey opened this issue Jun 11, 2020 · 0 comments
Open

-s in secrets engine makes them unreadable #240

mike-bailey opened this issue Jun 11, 2020 · 0 comments

Comments

@mike-bailey
Copy link

mike-bailey commented Jun 11, 2020

At least the Logical endpoints improperly URL encodes - and thus if you have something, say, called secrets-kv it won't be able to list, read, etc as it'll encode - and fail. Vault CLI doesn't encode -.

I tapped the list functions from logical to client and confirmed:

{:list=>true}

"/v1/secrets%2Dkv"

#<URI::HTTPS https://websitehere/v1/secrets%2Dkv?list=true>```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant