-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle session expiration time issue #89. #94
Open
fknives
wants to merge
21
commits into
develop
Choose a base branch
from
issue#89
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request is intends to resolve issue #89.
The main idea is to take advantage of the
expires_in
response from the server.Whenever we know the token is already expired, we don't need to send out a request that is certain to fail at least with 401 (if no other network issue is there like DNS, server availability etc).
Without this:
-> tokens are expired
-> request goes out
-> gets 401
-> authenticator refreshes the tokens
-> request is resent with updated tokens
-> data received
With the current changes:
-> tokens are expired
-> expiration timestamp is checked, signaling expiration
-> authenticator refreshes the tokens
-> request is sent with updated tokens
-> data received
For backwards compatibility this is not enabled by default. To take advantage of this a separate
TokenExpirationStorage
has to be implemented. A combined SharedPref storage for bothTokenExpirationStorage
andAuthenticationLocalStorage
is implemented.