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

Allow to set password_encryption algorithm #144

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

op
Copy link

@op op commented Aug 15, 2024

Description of changes:

This allow you to override the encryption algorithm used by the server when storing the password to support legacy clients like Redshift.

Redshift is not able to connect to PostgreSQL with scram-sha-256. This message is returned:

authentication method 10 not supported

Possibly Redshift is using an old version of libpq which only support md5. This change fixes the problem for us.

References:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This allow us to set the password encryption algorithm that the server
uses to store the password to support legacy clients to authenticate.
@simonmarty
Copy link
Contributor

We provide a Redshift rotation lambda, are you not able to use that one instead?

@op
Copy link
Author

op commented Oct 28, 2024

I don't believe that one works for PostgreSQL. This is for changing the password in PostgreSQL and optionally specifying the encryption method used (eg one that is supported by Redshift). Newer versions of PostgreSQL uses an password encryption method that is not supported by Redshift (or older versions of libpq) so this allow us to keep backwards compatibility.

You can connect from Redshift to PostgreSQL with an external schema.
https://docs.aws.amazon.com/redshift/latest/dg/r_CREATE_EXTERNAL_SCHEMA.html

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

Successfully merging this pull request may close these issues.

2 participants