You can override backend login application to simply redirect any request to frontend application and put all logic there, i.e. let it make decision on who is logged in and were redirect him to.
Cross application links would be helpfull also. On Tue, 2009-03-03 at 12:00 +0100, Tomasz Ignatiuk wrote: > OK, but when I add authentication (Security on) I cannot define an > application. It uses own application. So when session is gone it want > redirect me to loginapp but to frontend/backend. > > 2009/3/3 David Herrmann <[email protected]> > > Tomasz Ignatiuk wrote: > > I don't get it...But witch action should be targeted in > form? To > > backend, or to frontend? > > > I think this depends on your personal taste. But if don't like > either > solutions why not create a third application (besides frontend > and > backend), e.g. "loginapp", that handles only login and > redirection to > the appropriate frontend or backend controllers? > > From a security point of view this would also be elegant: > then you can > require authentication and/or credentials on all frontend and > backend > apps and make the login app open to visitors. > > David > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
