as per question, there's way change redirect url servicestack auth services.
however, when inheriting controllers servicestackcontroller<authuserservice>
doesn't work because servicestackcontroller hardcodes redirect url , changing in authfeature
registration has no effect on it.
my questions are:
1) correct way go around problem?
there option override loginredirecturl
, it? what's point of authenticate attribute's htmlredirect
property or authfeature's one?
2) , purpose of servicestackcontroller
altogether?
3) have put [authenticate]
on base controller , [authenticate]
attribute seems ignore [allowanonymous]
attribute put on login
actions of account controller.
i know 2 separate , [allowanonymous]
coming system.web there "allow" attribute in servicestack?
i assuming using servciestack alongside asp.net mvc application...
1) correct way go around problem?
in mvc controller inherits servicestackcontroller added handling redirects.
public override actionresult authenticationerrorresult { { if (this.authsession == null || this.authsession.isauthenticated == false) { return redirect("~/home/login"); } return base.authenticationerrorresult; } }
what's point of authenticate attribute's htmlredirect property or authfeature's one
i'm pretty sure htmlredirect
works expected when not making requests mvc controllers (ie. calling /api/foo, assuming servicestack's custompath '/api'). think there issues mvc 'hijacking return'.
2) , purpose of servicestackcontroller altogether?
understanding it's main purpose share session data between servicestack , mvc
but there "allow" attribute in servicestack?
not aware of since authenticate filter create subclass of , add type of support 'allow'.
Comments
Post a Comment