Hi Vincent, Thanks for taking the time to read my post.
At first I tried access_denied_url and access_denied_handler as well, but I noticed they weren't getting called when requesting paths for which I had insufficient credentials. I am still not sure what the access_denied_handler is for. That said, my problem is not that I cannot intercept the authentication failure and return a custom response. My problem is that I don't know how to retrieve the login_path belonging to the firewall definition that the request failed to authenticate against. I have a Request available. I can use that request to get an AuthenticationListener from the FirewallMap but that gets me nowhere. I could try to forward to the default FormEntryPointHandler but will need to know the id that is prepended to the service id which is probably based on the firewall id, which brings me back my original problem. Besides I don't know in what scope my custom handler is called but the EntryPoint handlers are defined as private services so I am not sure I can even get at them. Best, Dirk Louwers On 13 mei, 10:51, Vincent Lechemin <vincent.leche...@gmail.com> wrote: > I'm not sure if it is the right way either, but my way to do this is > to define a custom path for 403 errors, > security: > access_denied_url: /error/403 > and then use the custom controller to handle the wanted behavior. > > -- > Vincent -- 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 users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
