[10.x] Do not add token to AWS credentials without validating it first #48297
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.
In the
CacheManagerandFilesystemManagerthe config that is used to instantiate a new AWS client checks forkeyandsecretvalues within provided array, before adding those to thecredentialselement of the config. Unfortunately it also adds atokenvalue, without a similar validation - which can lead to including a blanktokenvalue unnecessarily.Worse still, including a blank
tokenvalue within that config'scredentialsarray can cause requests using these clients to fail - producing errors such as this when using aDynamoDbClient(which extends theAwsClient) created by aCacheManagerthat has included such a blanktokenvalue:Not including a (blank)
tokenvalue in the config fixes this problem.