-
-
Notifications
You must be signed in to change notification settings - Fork 420
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
Added pgbouncer authentication via auth_user and auth_query #401
Added pgbouncer authentication via auth_user and auth_query #401
Conversation
Related Issue #334 |
@chuegel Thank you for your PR I will look carefully at the code tomorrow. In the meantime, I would like to invite you to read the article https://www.enterprisedb.com/postgres-tutorials/pgbouncer-authquery-and-authuser-pro-tips perhaps after reading the article you will make a few more commits ;) |
@vitabaks thanks, I will look into it. The PR can be improved for sure. |
@chuegel Let me know if you need my help in finalizing this PR. |
…when pgbouncer_auth_username is enabled
use 'true' instead of 'yes'
We have removed the 'pgbouncer_generate_userlist' variable because now the pgbouncer authentication method ('auth_file' or 'auth_user, auth_query') is managed using the 'pgbouncer_auth_user' variable.
Thank you @chuegel good job! |
Hi,
following this discussion, the PR adds the possibility to use only one user to query the database and perform the authentication via pgbouncer auth_user and auth_query.
This will create dynamic pools for each dbname+user combination.
I've tested it with a 3 node Ubuntu 22.04 LTS cluster but I guess it will need additional distributions to run test against.
CAVEAT:
this only works if the password for the auth_user is set in plaintext in userlist.txt because there is no actual client doing SCRAM authentication against the database.