I'm currently working on a external login system by using some of ASP.NET standard API methods and attributes.
I therefor also use a normal MVC controller by custom routing and a normal View for avoiding Umbraco to take over the controller, methods etc.
Everything is working great until i use the "Authorize" attribute. As soon as this attribute is set, it seems like Umbraco redirect the page to be a Umbraco backoffice login page, and i can't really figure out a way to work around it.
I hoped someone here maybe know how to avoid the scenario or maybe have an idea how to avoid it.
External login issue
I'm currently working on a external login system by using some of ASP.NET standard API methods and attributes.
I therefor also use a normal MVC controller by custom routing and a normal View for avoiding Umbraco to take over the controller, methods etc. Everything is working great until i use the "Authorize" attribute. As soon as this attribute is set, it seems like Umbraco redirect the page to be a Umbraco backoffice login page, and i can't really figure out a way to work around it.
I hoped someone here maybe know how to avoid the scenario or maybe have an idea how to avoid it.
Thanks in advance!
Custom routing:

Controller:

Return page:

is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.