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
Describe the bug
When an API call is made that requires an authenticated user, the app currently fails without giving a clear reason to the user. In cases where the API returns an "Unauthorized" response, we should redirect the user to the login page.
To Reproduce
Steps to reproduce the behavior:
Log in to the application
Visit the search page
Allow the session token to expire, but stay on the search page
Attempt to make a search.
-- OR --
Navigate to the search page by using the URL without being logged in
Attempt to make a search
Expected behavior
When a user attempts to perform a task that requires them to be logged in, they should be taken to a login page.
Screenshots
Additional Context
Server returns a 422 status code in this case.
Response: {"msg":"Signature verification failed"}
The text was updated successfully, but these errors were encountered:
Describe the bug
When an API call is made that requires an authenticated user, the app currently fails without giving a clear reason to the user. In cases where the API returns an "Unauthorized" response, we should redirect the user to the login page.
To Reproduce
Steps to reproduce the behavior:
-- OR --
Expected behavior
When a user attempts to perform a task that requires them to be logged in, they should be taken to a login page.
Screenshots
Additional Context
Server returns a 422 status code in this case.
Response:
{"msg":"Signature verification failed"}
The text was updated successfully, but these errors were encountered: