You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the JWT expiration is set to 24hours. To avoid token expiration and logging out of an active user, a token refresher is required. This will function in a way that if a user has not interacted with the application with their account in the past 7 days, they will need to log back in. Otherwise, the token will be refreshed. Additionally, when the user's token is expired, this is not handled in the application and the unauthorized API calls simply lead to a non functional app. When a token is expired, the user should be redirected to the login page, stating that the session has ended.
NOTE: Considering the low priority of #76 and #77, #244 will be prioritized and will be completed independently.
Currently, the JWT expiration is set to 24hours. To avoid token expiration and logging out of an active user, a token refresher is required. This will function in a way that if a user has not interacted with the application with their account in the past 7 days, they will need to log back in. Otherwise, the token will be refreshed. Additionally, when the user's token is expired, this is not handled in the application and the unauthorized API calls simply lead to a non functional app. When a token is expired, the user should be redirected to the login page, stating that the session has ended.
NOTE: Considering the low priority of #76 and #77, #244 will be prioritized and will be completed independently.
[SP: Iteration 11 - 3 SP]
[Priority: 76 & 77 Low, 244 High]
[Risk: low]
The text was updated successfully, but these errors were encountered: