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
While logged in, if I try and go to the login screen (at /), the screen is presented so that I can log in as someone else. If I log in as someone else, I am logged out To Reproduce
Steps to reproduce behaviour:
Log in to application
Return to / path by changing browser URL
Observe that login screen is available, even though I should in theory be logged in.
Severity
Mark with an x.
Minor effect eg. graphical
Functional error eg. App does not function correctly
Severe eg. Crashing
Reproducibility
Mark with an x.
Consistent
Occasional
Cannot reproduce at the moment eg. unsure
Expected behavior
I cannot access the login screen while logged in, and must log in to do this.
I suggest that we solve this issue by removing the /home part of the route for the logged in part of the application and serving everything there directly from / (i.e. also /transactions instead of /home/transactions and so on) and while the user is logged in. This would mean that the log in screen is not accessible, and the routing would look cleaner.
Screenshots, Images and Traces
Not applicable
Conditions
Tested on Windows with Chromium-based Edge but this should be reproducible on any browser.
Also, this shouldn't be fixed unless #142 is addressed. Otherwise, the user would not be able to log in as anybody else once logged in, since they can't currently actually sign out.
Additional context
Not applicable
The text was updated successfully, but these errors were encountered:
Describe the bug
While logged in, if I try and go to the login screen (at
/
), the screen is presented so that I can log in as someone else. If I log in as someone else, I am logged outTo Reproduce
Steps to reproduce behaviour:
/
path by changing browser URLSeverity
Mark with an x.
Reproducibility
Mark with an x.
Expected behavior
I cannot access the login screen while logged in, and must log in to do this.
I suggest that we solve this issue by removing the
/home
part of the route for the logged in part of the application and serving everything there directly from/
(i.e. also/transactions
instead of/home/transactions
and so on) and while the user is logged in. This would mean that the log in screen is not accessible, and the routing would look cleaner.Screenshots, Images and Traces
Not applicable
Conditions
Tested on Windows with Chromium-based Edge but this should be reproducible on any browser.
Issue Dependencies
Related to #141.
Also, this shouldn't be fixed unless #142 is addressed. Otherwise, the user would not be able to log in as anybody else once logged in, since they can't currently actually sign out.
Additional context
Not applicable
The text was updated successfully, but these errors were encountered: