feat(auth): Removed dependency on oauth2 token for refreshToken and move to initiateAuth for hostedUI #3497
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.
Issue #
#3496
Description
Currently we use oauth2/token endpoint to refresh tokens when the user is logged in via HostedUI. The premise of this was you need to refresh using the hostedUI api to preserve custom scopes. Service team has confirmed that we do not need to call the hosted UI endpoint api for refreshing of the tokens and simply calling the initiateAuth api will also preserve custom scopes as long as the sign in was done using the HostedUI api.
Furthermore, this brings us in parity with other platform implementations. Android and Flutter already does refreshing of tokens this way.
Android PR: https://github.com/aws-amplify/amplify-android/pull/2543/files
General Checklist
Given When Then
inline code documentation and are named accordinglytestThing_condition_expectation()
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.