-
Notifications
You must be signed in to change notification settings - Fork 222
Add support for client SCRAM authentication #255
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
Comments
I'm connecting pgcat to readyset(using default config) and get error is it something related to this issue? |
https://www.postgresql.org/docs/current/protocol-message-formats.html That's not great, clear text authentication should not be used generally speaking. This has nothing to do with this issue. Pgcat does not implement clear text authentication for servers or clients. |
Seconding this; we'd switch from pgbouncer to pgcat if there was support for SCRAM passthrough |
"Cleartext" over authenticated TLS is actually more secure than md5 over authenticated TLS. Because of the way the protocol works the md5 hash becomes the effective password. This hash is then stored plaintext in the database, thus storing the effective password plaintext in the database. Cleartext + authenticated TLS + scram storage does not have this problem. |
Hi, |
Haven't had a chance to implement this yet. A PR is welcome. |
Is your feature request related to a problem? Please describe.
Postgres 14 switched the default password encryption and authentication method from Md5 to SCRAM-SHA-256. PgCat can authenticate to the servers using SCRAM, but it can't authenticate clients using SCRAM, only Md5. Client libraries still support Md5, but medium/long term Postgres is sure to remove that insecure authentication algorithm from
libpq
, so we need to add support for SCRAM for client auth as well.Describe the solution you'd like
Add support for client-initiated auth to
scram.rs
and add support for it inclient.rs
.Describe alternatives you've considered
There aren't any, this is a necessary change.
Additional context
#253
The text was updated successfully, but these errors were encountered: