SCRAM-SHA-256 support #643
Conversation
poloz-lab
force-pushed
the
scram_sha_256_limited_support
branch
2 times, most recently
from
cdf8b8f to
20b627a
Compare
- auth_mechanism parameter for mongodb_user - use password instead of password_hash if SCRAM-SHA-256, because password digestion is on the server - insync is not verified for the password
poloz-lab
force-pushed
the
scram_sha_256_limited_support
branch
from
20b627a to
e6d8a53
Compare
poloz-lab
force-pushed
the
scram_sha_256_limited_support
branch
from
e6d8a53 to
b042af0
Compare
GitHub drop support for git:// url a while ago.
|
Thanks, I added 2 commits to your branch to fix CI. I'll let MongoDB users review the PR and test that the feature works as expected. |
|
Thanks @smortex , I'm working on adding some spec to test if the authentication mechanism selection work as expected. |
poloz-lab
force-pushed
the
scram_sha_256_limited_support
branch
9 times, most recently
from
c251895 to
18e6c8a
Compare
The version of MongoDB used in CI tests doesn't support SCRAM-SHA-256 (except for debian10 machines) |
ghost
mentioned this pull request
The module seems to need some love : CI test against rather old OSes, at least Debian 9 should not be here and Debian 11 should :-) If you think some old stuff prevents you from working efficiently with this codebase, maybe it is okay to slash the legacy support? |
Pull Request (PR) description
Add limited support for SCRAM-SHA-256 authentication mechanism.
Limited because we loose the ability to check if the password is insync when SCRAM-SHA-256 is used.
The password is no longer digested on the client.
The second commit add the possibility to force the update of the password manually with a boolean.
This Pull Request (PR) fixes the following issues
Fixes #597