Authentication and Password Resolution Improvements#62
Merged
ric-v merged 3 commits intodev-asterix:mainfrom Mar 15, 2026
Merged
Authentication and Password Resolution Improvements#62ric-v merged 3 commits intodev-asterix:mainfrom
ric-v merged 3 commits intodev-asterix:mainfrom
Conversation
…n logic, fixing authentication resilience and connection configuration stripping.
This file contains hidden or 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
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 pull request introduces several improvements and fixes focused on authentication and connection handling, especially regarding
.pgpassfile support and password resolution logic. The changes enhance compatibility with standard PostgreSQL password file conventions, improve fallback reliability, and make the authentication process more robust and transparent.Authentication and Password Resolution Improvements:
.pgpassfiles (and Windows%APPDATA%\postgresql\pgpass.conf), including explicit parsing and resolution logic to match standard PostgreSQL behavior. [1] [2] [3].pgpass(only for explicit usernames), with clear fallback to handle trust authentication and SCRAM errors gracefully. [1] [2].pgpasslookup scope to avoid implicit machine name environments, ensuring backward compatibility for local trust authentications. [1] [2]Connection and Client Configuration Reliability:
DatabaseTreeProvidercould strip configuration details (such as inline passwords andsslmode) during fallback calculations by ensuring the full connection object is passed through. [1] [2]Other:
0.8.7and added a detailed changelog entry for these enhancements and fixes. [1] [2]