-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[database/postgres] Vault generates credentials that do not work with AWS redshift #4052
Comments
Still broken :( |
@myoung34 did you ever solve this? |
I use a bash script to manually lower case |
@myoung34 behold the redshift plugin that works with database engine: https://github.com/andoriyu/vault-plugin-database-redshift |
Can confirm the problem lies within the username not being lower-cased. |
I just forked official postgres driver and forced lowercase in it. Works
well.
…On Fri, Aug 9, 2019, 8:15 AM Aaron Walker ***@***.***> wrote:
Can confirm the problem lies within the username not being lower-cased.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#4052?email_source=notifications&email_token=AABEFG6EWSI6HOJMQZVD3D3QDWC27A5CNFSM4ES4JXFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD366ZUY#issuecomment-519957715>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABEFG776OU6XNQC4MO5AT3QDWC27ANCNFSM4ES4JXFA>
.
|
How did you create the plugin? Did you rebuild Vault from source or did you install it separately? I tried to use the binary created by |
I've rebuild plugin from source, not entire vault. Installed it like any
other custom plugin and it worked fine. I'll see if I can find source.
I do still the binary though.
…On Sat, Aug 10, 2019, 12:21 PM Aaron Walker ***@***.***> wrote:
How did you create the plugin? Did you rebuild Vault from source or did
you install it separately? I tried to use the binary created by go install
but it did not work. Also, I do not see where you lower-cased the username
in your code.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#4052?email_source=notifications&email_token=AABEFG247EUGCE2T6W7TXNLQD4IJ3A5CNFSM4ES4JXFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4ATOIY#issuecomment-520173347>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABEFG2TE3DYTQUEYYK63ETQD4IJ3ANCNFSM4ES4JXFA>
.
|
@walkafwalka here is the source for plugin I'm running: https://github.com/andoriyu/vault-plugin-database-redshift (i didn't commit my last change where I actually lower case it) it's just copy of https://github.com/hashicorp/vault/tree/master/plugins/database/postgresql with a few things renamed and downcasing. You also need to make sure you compiled your thing for platform vault is running on. |
Closed by #8299 |
Environment:
0.9.4
Ubuntu client, AWS Linux server, Redshift database
Vault Config File:
Startup Log Output:
Expected Behavior:
Generate valid users similar to currently working RDS PSql 9.6
Actual Behavior:
Generates users successfully but incorrectly returns username if contains capital letters.
Redshift is PSQL 8 and generates lower case usernames even if capital letters provided. Vault is unaware and attempts to create user 'Foo', successful, stores it as 'Foo' and tells the user that their username is 'Foo'. However redshift stores 'foo' so you cannot login directly with vault's response, and have to lower() the username.
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: