Support authentication mechanism negotiation #38
Merged
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.
...by adding
saslSupportedMechs: <db.user>
to the hello command. This will return an additional fieldhello.saslSupportedMechs
in its result.Negotation
If an authentication mechanism is explicitely supplied via the connection string, it's used regardless of what the server answers. Otherwise, negotation tries to find the preferred authentication mechanism.
(see https://github.com/mongodb/specifications/blob/master/source/auth/auth.rst#defaults)
?authMechanism=SCRAM-SHA-256
?authMechanism=SCRAM-SHA-1
?authMechanism=PLAIN
Errors
Real-life examples
...when adding a
var_dump()
of the returned hello.saslSupportedMechs key:Local 5.0.20 (Ubuntu)
MongoDB Atlas