Johannes, Not sure about right topic, but seems your commit affects me also. If I introduce a success_handler it should return a response, or I get an exception. In my case I just want to get things processed only if $request- >isXmlHttpRequest(). And if request is a general HTTP request it would be cool to get your code in action. But I can't override "onSuccess" and "onFailure" as they are private, and can't replace them as "handle" is final now. I was just checking if success_handler isset and returns null - going as parent does. Same with failure_handler
Maybe we are both on wrong way of dealing with ajax auth? Artem. On Jun 18, 11:41 am, Johannes Schmitt <schmitt...@gmail.com> wrote: > Can you explain this a bit more? This should be compatible with Ajax > requests unless the very first request goes to the check_path. I don't see > when this would happen though except for the cases stated in the exception > message. > > Johannes > > On Fri, Jun 17, 2011 at 8:28 PM, Stefan Paschke > <symfony.pasc...@gmail.com>wrote: > > > > > > > > > Hi > > > commit 28bee92c75ad2e02ea229f4dd064372f00a68cdb by Johannes introduced a > > new $request->hasPreviousSession() check to > > AbstractAuthenticationListener::handle(), which causes authentication > > requests to fail if no previous session is available, even if the actual > > authentication process ran through. > > I have been using the UsernamePasswordFormAuthentication without redirects > > (by directly accessing the check_path and configuring a custom > > successHandler, in order to authenticate via ajax or backend request), which > > is not possible any more. Since AbstractAuthenticationListener::handle() is > > final, there also is no easy way to change this behaviour by extending the > > Listener class. So while I think the hasPreviousSession() is useful in a > > regular setup, it should be configurable or at least extendable. What are > > your opinions on the topic? > > > best regards > > > Stefan > > > -- > > If you want to report a vulnerability issue on symfony, please send it to > > security at symfony-project.com > > > You received this message because you are subscribed to the Google > > Groups "symfony developers" group. > > To post to this group, send email to symfony-devs@googlegroups.com > > To unsubscribe from this group, send email to > > symfony-devs+unsubscr...@googlegroups.com > > For more options, visit this group at > >http://groups.google.com/group/symfony-devs?hl=en -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
