fix(Authenticator): Handling expired sessions #87
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 #, if available:
Description of changes:
When a user session cannot be refreshed,
Amplify.Auth.fetchAuthSession()
will still returnisSignedIn: true
, but attempting to perform any operation that requires authentication will subsequently fail and ask the user to log in again.This is a known thing within Amplify, but can be handled by the Authenticator by signing out the user if we detect their session has expired when the component is launched.
This PR proposes validating that a session has valid identity ID and/or Cognito tokens, depending on what type of configuration the user is using:
CognitoIdentity
, only check for a valid `session.getIdentityId()CognitoUserPool
, only check for validsession.getCognitoTokens()
.session.getIdentityId()
andsession.getCognitoTokens()
.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.