That's a pretty cool feature I hadn't noticed, but it looks like FailureHandlers are fired only on an unsuccessful login attempt, not on every request. So it wouldn't be an option for dealing with this issue.
Thanks for that though :) On Jun 10, 12:50 am, Stefan Paschke <symfony.pasc...@gmail.com> wrote: > you would not need to extend the existing listener, you could just add a > FailureHandler Service to your Firewall that could take care of that. > Configuration is described in the > referencehttp://symfony.com/doc/current/reference/configuration/security.html, > the service class would have to extend > Symfony\Component\Security\Http\Authentication\AuthenticationFailureHandler > Interface > > regards > > Stefan > > > > > > > > > So is there a "right" way to deal with this issue in Symfony2? > > Perhaps extending an existing listener? Could be a useful cookbook > > article. (and i apologize if this has been addressed somewhere, but I > > did my due diligence) > > > -- > > 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
