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
I think the issue is that the # character has special meaning in URLs. So because we create a connection_url and expand {{password}} to be something with a #, that breaks parsing of the expanded URL. I don't see any potential workaround here, other than not using that character.
Describe the bug
Trying to setup Postgres Backend from official guide https://www.vaultproject.io/docs/secrets/databases/postgresql.html and getting an pg error.
My password contains symbol
#
and that seems an error for parsing (or validation) of my config.To Reproduce
Steps to reproduce the behavior:
vault secrets enable database
vault write database/config/my-postgresql-database \ plugin_name=postgresql-database-plugin \ allowed_roles="my-role" \ connection_url="postgresql://{{username}}:{{password}}@localhost:5432/" \ username="root" \ password="root#"
Expected behavior
My PostgreSQL allows me symbol
#
in password. I spent a lot of time finding what exactly broken my config :)Environment:
vault status
): 1.1.2vault version
): v1.1.2 ('0082501623c0b704b87b1fbc84c2d725994bac54')Vault client MacOS
The text was updated successfully, but these errors were encountered: