-
Notifications
You must be signed in to change notification settings - Fork 462
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
GSS Auth Implementation #1209
base: master
Are you sure you want to change the base?
GSS Auth Implementation #1209
Conversation
Just as with the LDAP PR it would be very helpful if someone that uses GSS could try this PR out. I can do a review to see if the code looks sensible, but I don't really know enough about GSS to do an indepth review of this (nor do I have the time to learn). |
FYI while cleaning up old PRs I found this one: #441 It would probably be good to check if there are any good ideas in there. |
I did see that. Definitely took some ideas from that in terms of how to interact with the GSS API from it. |
Expanded the test coverage and feature set. Tried to match all of the GSS options that are available in postgres (case insensitive match, realm match, etc). I believe that I have everything covered currently with the exception of user mapping. |
This PR implements GSS authentication in pgbouncer. This is a very important institutional feature that allows a client to verify its identity to a server (and vice versa) without the client ever sending its password to the server.
Since the underlying gss c functions are network blocking and synchronous I used the threaded design common to the PAM implementation and the LDAP PR #731 use for this functionality. For the CI and testing aspects of this PR I found the GSS backend encryption PR #743 helpful as well.
Sources: