feat(auth): support clientmetadata for token refresh #14556
Draft
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 of changes
Adds support for dynamically providing client metadata for Cognito token refresh operations through a
ClientMetadataProvider
function type. More specifically:• Added
ClientMetadataProvider
function type to @aws-amplify/core types• Added
setClientMetadataProvider()
method toCognitoUserPoolsTokenProvider
• Integrated
ClientMetadataProvider
intoTokenOrchestrator
for token refresh operations• Added async client metadata provider support to token refresh flow
• Updated tests for new functionality
Usage
Issue #, if available
#13379
Description of how you validated changes
• Added unit tests for setClientMetadataProvider functionality
Checklist
yarn test
passesChecklist for repo maintainers
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.