Treats Expires_in and x_refresh_expires_in as elapsed time in seconds. #20
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 PR fixes an inconsistency with timestamps within the project.
The current code treated the
expires_inandx_refresh_expires_inas timestamps if they were passed in as constructor parameters. If a token was set using thesetTokentheexpires_inandx_refresh_expires_inbecame timestamps fromDate.now(). This lead to inconsistent behavior in the validation methods depending on how you created the token.To handle stored tokens, an optional
createdAtparameter was created. This stored tokens to have the correct expiration date, instead of usingDate.now().