Add Support for the PLAIN authMechanism #223
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
* Add support for LDAP authentication * Unit test for url parser changes
* Mention PLAIN auth support in the Readme * tweak wording
|
Thank you! |
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.
PLAIN authentication is supported by MongoDB Enterprise Edition and MongoDB Atlas when those servers are configured to an external LDAP identity provider for user management. I needed to support this mechanism from Elixir for a customer engagement. Posting those changes here for potential upstreaming.
The mechanism itself is extremely simple. Username and password are sent to the server in plain text and either accepted or rejected. It is assumed that the underlying connection is encrypted but this is not enforced. I did need to tweak the URL parser code to allow url-encoded values for the
authSourceoption. The auth source must be set to "$external" when using this mechanism and so will be encoded.Unfortunately, I don't currently have a solution for automated testing of this mechanism, as it requires a paid version of the database and a bit of setup to use.