feat(NODE-7047)!: use custom credential provider first after URI #4656
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
3 tasks
durran
force-pushed
the
NODE-7047
branch
2 times, most recently
from
1a59a5a to
6e98b5d
Compare
dariakp
changed the title
durran
force-pushed
the
NODE-7047
branch
3 times, most recently
from
7281459 to
8271c1f
Compare
durran
changed the title
baileympearson
added
the
Primary Review
dariakp
previously requested changes
Sep 22, 2025
baileympearson
requested changes
Sep 22, 2025
baileympearson
approved these changes
Sep 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
Updates AWS auth to use a custom credential provider first after URI/MongoClient credentials if present.
Summary of Changes
What is the motivation for this change?
NODE-7047
NODE-6987
Release Highlight
Custom AWS Credential Provider Takes Highest Precedence
When providing a custom AWS credential provider via the auth mechanism property
AWS_CREDENTIAL_PROVIDER, it will now take the highest precedence over any other AWS auth method, with the exception of URI parameters or credentials passed directly to theMongoClient.Double check the following
npm run check:lint)type(NODE-xxxx)[!]: descriptionfeat(NODE-1234)!: rewriting everything in coffeescript