I have been having the exact same problem since this morning.
And I haven't come up with a solution since unfortunately...
On Mar 8, 2:56 pm, Donald <chekot...@gmail.com> wrote:
> OK, I modified the security.yml file as follows:
>
> # app/config/security.yml
> security:
> access_denied_url: /error403
>
> providers:
> entity:
> entity: { class: UserBundle:User, property: username }
>
> firewalls:
> main:
> form_login:
> check_path: /login_check
> login_path: /login
> failure_path: /login
> logout: true
>
> And I still get the following error after submitting the login form:
>
> Unable to find the controller for path "/login_check". Maybe you
> forgot to add the matching route in your routing configuration?
>
> On Mar 7, 2:27 pm, Christophe COEVOET <s...@notk.org> wrote:
>
>
>
>
>
>
>
> > Le 07/03/2011 21:24, Donald a crit :> Christophe,
>
> > > Thanks for the response.
>
> > > I'm aware that there are certain features missing from my example
> > > above. But I'm trying to keep this test case very limited so I can
> > > concentrate on the problem at hand; being that the check
> > > authentication is not working.
>
> > Sure, but your issue can be this: when the authentication fails, the
> > request is not redirected so you need to have a controller. Thus it
> > would display the authentication error (which also appear in the logs if
> > you log debug messages)
>
> > --
> > Christophe | Stof
--
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
