feat: add support for SCRAM authentication in mongo/DocumentDB #1089
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.
Related Issue
Closes: #1016
Describe the changes you've made
Added functions to generate the new responses of the SCRAM authentication requests. And uses these functions to pass authentication in test mode for the DocumentDB which uses SCRAM-SHA-1. The user have two ways to pass the authentication for testing:
default123
) for testing environments. Example: if an API is using an environment variableMONGO_PASSWORD
for the creating a mongo url to connect. Then, change the value of the environment variable to "default123" for testing environment so that the keploy generated testcases pass.--mongoPassword
to use their password with which they have recorded the testcases.Type of change
Please let us know if any test cases are added
Have used the sample-go/gin-mongo, tested the changes along with documentDB.
Describe if there is any unusual behaviour of your code(Write
NA
if there isn't)A clear and concise description of it.
Checklist: