Details
-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
None
Description
Milestone (pre-alpha, alpha, finished release)
finished release, not necessarily needed
Estimated Complexity
structural
Description
In the angular-based app, the login page redirects to the previously visited page. This is no longer possible the same way: the pages are now separated and login cannot store the angular context like before
Possible Solution
- we already have login as an react component
- angular components redirect to /login on 401, therefore we can't stay on the same page and render something over it
- Maybe we can work with browser history?