I have the dashboard implemented and working as expected using Root “/” so when user visit the URL the user needs to login and after success the user will be taken directly to the dashboard.
the issue is if the user close the browser and reopen and try to visit the URL again, no authentication is populated and the user will be presented with the dashboard right away.
the question is how to implement a signout button in the dashboard to logout the user when clicked without having the user go to /admin page to signout.
Note: in the above scenario users are not and should not be aware of /admin page.
Yes, I can confirm what @wsl2001 said as well. It executes the signoff API call and then just “sits” there.
A redirect to the login screen should be triggered just after the signout and then it would be perfect!
Thanks for having fixed that issue in a recent release.
However would it be possible to slightly improve the redirection after the logout?
Right now you do a normal redirect to /login.
The problem with that is that if you try to login again with an account that has admin rights, you’re automatically logged-on into the admin interface. Maybe that’s not something you want.
So would it be possible to include the ReturnUrl as well in the redirection page after a logout is performed? Like that when somebody logs back in it lands automatically on the Dashboard where he has left.
…hope this makes sense, otherwise I’m glad to understand how I can manage this “dynamic” Dashboard assignment / redirection based on role membership… Maybe I’ve missed something in the docs…?