Is it possible to extend the login screen / controller to redirect to a frontend page after successful login?
The current implementation (with a returnPath pseudo querystring parameter) can only redirect inside the backoffice (it seems?), because well, Angular, I guess...
I'd love to be able to specify something like returnPath=/dashboard/today and have it work.
The highlighted line in the link above is invoked on a successful login. That line can be modified to redirect the user somewhere else. I briefly tested that, and it seems to work like a charm.
However you're probably looking for a way to solve this without modifying Umbraco core files. I'm not an Angular expert, but I don't think is possible to without modifying core files - at least at the moment.
If this is a feature people need, perhaps you could update the line to trigger some kind of Angular event, that developers then can hook into, and then create a pull request.
But as always when working with login, we need to think about any potential security issues a change like this could raise. So perhaps the best thing to do, is to create an issue on the tracker, and start a discussion with the people from the HQ, and then take it from there ;)
Specify login screen returnPath to frontend
Hi all,
Is it possible to extend the login screen / controller to redirect to a frontend page after successful login?
The current implementation (with a
returnPath
pseudo querystring parameter) can only redirect inside the backoffice (it seems?), because well, Angular, I guess...I'd love to be able to specify something like
returnPath=/dashboard/today
and have it work./Chriztian
I'm trying to do something similar to this as well and would love to know if someone has an answer :)
Just a little follow up to the conversation on Twitter:
https://github.com/umbraco/Umbraco-CMS/blob/dev-v7/src/Umbraco.Web.UI.Client/src/views/common/dialogs/login.controller.js#L116
The highlighted line in the link above is invoked on a successful login. That line can be modified to redirect the user somewhere else. I briefly tested that, and it seems to work like a charm.
However you're probably looking for a way to solve this without modifying Umbraco core files. I'm not an Angular expert, but I don't think is possible to without modifying core files - at least at the moment.
If this is a feature people need, perhaps you could update the line to trigger some kind of Angular event, that developers then can hook into, and then create a pull request.
But as always when working with login, we need to think about any potential security issues a change like this could raise. So perhaps the best thing to do, is to create an issue on the tracker, and start a discussion with the people from the HQ, and then take it from there ;)
is working on a reply...