Implement Trust Authentication #805
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@drdrsh Any chance you can review this PR? It's tested, doesn't require any changes to the CI docker image, and has no breaking changes. |
drdrsh
reviewed
Sep 10, 2024
drdrsh
reviewed
Sep 10, 2024
|
@drdrsh Last commit fixed the above 2 issues and cleaned up the tests a bit (implemented proper setup/teardown so a test failure doesnt leave a lingering pgcat server in the test environment, moved the trust pgcat config to a temp file generated by python so that the config is collocated with the relevant test. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements trust (no password authentication). This is somewhat related to #748 and has some overlapping changes but this PR does not require any changes to the dockerfile/CI.
This feature reflects postgres' implementation documented here.