This repository was archived by the owner on Jul 5, 2025. It is now read-only.
Add support for MongoDB authentication #8
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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 commit adds support for user mappings to mongo users. This requires that you specify
use_auth 'true'in the server options when using authentication.The reason for adding the new
use_authoption is that PG's GetUserMapping function throws an error if none exists. I was unable to find a way to check if a user mapping existed without throwing an error that aborts the query. So we only call GetUserMapping if the server hasuse_auth 'true'.Look it over and let me know what you think!