Current Behaviour
When a user is not logged in and clicks a link, which contains private runs, user is directed back to index page.
Enhanced Behaviour
When a user is not logged in and clicks a link, which contains private runs, user is directed to login. If successfully logged in user is redirected back to view page.
Discussion
Note the SPWA uses Auth0 Universal Login for login. So we leave the SPWA environment
Currently I have thought of two methods to fix this issue:
-
The link, which contains the private runs, can be stored in local storage. When user logs in the run url is retrieved ,from local storage, and user is redirected.
-
The link, can be added as a parameter to auth0s callback (for example https://timeseries.com/callback.html?redirect=[RUNS_URL]).
Current Behaviour
When a user is not logged in and clicks a link, which contains private runs, user is directed back to index page.
Enhanced Behaviour
When a user is not logged in and clicks a link, which contains private runs, user is directed to login. If successfully logged in user is redirected back to view page.
Discussion
Note the SPWA uses Auth0 Universal Login for login. So we leave the SPWA environment
Currently I have thought of two methods to fix this issue:
The link, which contains the private runs, can be stored in local storage. When user logs in the run url is retrieved ,from local storage, and user is redirected.
The link, can be added as a parameter to auth0s callback (for example https://timeseries.com/callback.html?redirect=[RUNS_URL]).