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
Right now, if a session becomes expired, you can still use the site and get errors when trying certain things. Something should be done to ensure that if a session is expired, the user is unauthenticated.
For example, if a account is deleted and someone still has that account signed in on a page, they can still do stuff until they reload.
Requirements
Frontend
Backend
Investigate if there is a solution to this problem.
If there isn't or the solution is too complex, abandon this ticket and let Hayden know.
Acceptance Criteria
If sessions expire, the user should be forced to reload if it can be tracked.
Expired sessions should not cause rendering errors, all of that should be handled.
Expired sessions should not be authenticated to make requests.
Sessions should be preferably be updated rather than marked as stale requiring re-authentication.
Sessions should be revalided with getServerSession (existing authenticate method as used in API calls) as much as possible.
Notes
getServerSession, which is used in the authenticate method, should already update the session content.
If it isn't used, this content might not be updated.
Context
Right now, if a session becomes expired, you can still use the site and get errors when trying certain things. Something should be done to ensure that if a session is expired, the user is unauthenticated.
For example, if a account is deleted and someone still has that account signed in on a page, they can still do stuff until they reload.
Requirements
Frontend
Backend
Acceptance Criteria
Notes
getServerSession, which is used in the authenticate method, should already update the session content.
If it isn't used, this content might not be updated.
getServerSession
The text was updated successfully, but these errors were encountered: