-
Notifications
You must be signed in to change notification settings - Fork 145
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
feat: SASL client support #624
Comments
I'm happy to work on this! |
I've been doing this for the last two weeks. I don't have a lot of time, but I've already made a lot of progress. p.s. I'm not a PGCat contributor, so PR decisions are out of my hands. |
Is your feature request related to a problem? Please describe.
Currently, there is no client support for SASL authentication when connecting to the proxy
Describe the solution you'd like
Add SASL authentication as a configurable strategy. The default authentication mechanism will remain md5.
This will likely involve refactoring the authentication logic, possibly into a separate module.
The text was updated successfully, but these errors were encountered: