#166024717 Token verification and expiry for frontend & display user profile info #104
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
Add check for token expiration for a logged in user Add better loading screen graphic [Finishes #166024717]
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.
What does this PR do?
Checks for token expiration for a logged in user
Displays correct user information on the profile card
Adds better loading screen graphic
Description of Task to be completed?
Add verification of token on the frontend to log a user out when the token expires.
Display user's information in the profile page from the information generated from the token
How should this be manually tested?
VIsit the hosted pages here and login as any type of user and visit the
profilepage.Any background context you want to provide?
The JWT generated on the server expires after an hour and would not be valid, but it still gets added to requests from the frontend so there has to be a way to clear the token and generate a new one for new requests.
What are the relevant pivotal tracker stories?
#166024717
Screenshots (if appropriate)