Symfony login unable to find controller for path login_check despite being behind firewall

Question

I am having this rather common problem of Symfony login failing with this error message:

Unable to find the controller for path "/auth/login_check".

The common answer to this problem is that the login_check route isn't behind the firewall, but in my case it is! Here are my config files:

app/config/security.yml

firewalls:
    dev:
        pattern:    ^/(_(profiler|wdt)|css|images|js)/
        security:   false

    auth_area:
        pattern:    ^/auth/(login|login_check)
        anonymous:  ~

    secured_area:
        pattern:    ^/
        form_login:
            login_path: /auth/login
            check_path: /auth/login_check
        logout:
            path:   /auth/logout
            target: /

app/config/routing.yml

login:
    pattern: /auth/login
    defaults: { _controller: AuthBundle:Default:login }

login_check:
    pattern: /auth/login_check

logout:
    pattern: /auth/logout

AuthBundle/Controller/DefaultController.php

public function loginAction()
{
  $form = $this->createForm(new UserType(), new User());

  return $this->render('AuthBundle:Default:login.html.twig', array(
    'form' => $form->createView(),
    'action' => $this->generateUrl('login_check'),
  ));
}

AuthBundle/Form/Type/UserType.php

public function buildForm(FormBuilderInterface $builder, array $options)
{
  $builder->add('username', 'text', array('label' => 'Login:'));
  $builder->add('password', 'password', array('label' => 'Password:'));
}

AuthBundle/Resources/views/Default/login.html.twig

...
<form action="{{ action }}" method="POST">
  {{ form_widget(form) }}
  <input type="submit" value="Login" />
</form>
...

My form is created with the route login_check as target (/auth/login_check URL).

The secured_area firewall is supposed to match all URLs, so /auth/login_check should be in it. Yet, I keep getting this error. What am I doing wrong?

Emii Khaos · Accepted Answer · 2013-08-05 14:32:15Z

2

The login_check url must behind the same firewall as the using firewall. use ACLs instead.

firewalls:
    dev:
        pattern:    ^/(_(profiler|wdt)|css|images|js)/
        security:   false

    secured_area:
        pattern:    ^/
        form_login:
            login_path: /auth/login
            check_path: /auth/login_check
        logout:
            path:   /auth/logout
            target: /
        anonymous:  ~

access_control:
    - { path: ^/auth/login$, role: IS_AUTHENTICATED_ANONYMOUSLY }
    - { path: ^/, role: ROLE_USER }

answered Aug 5, 2013 at 14:32

Emii Khaos

10.1k3 gold badges37 silver badges57 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Jukurrpa Over a year ago

Doesn't this allow anonymous access to the whole website? By adding anonymous: ~ in the secured_area firewall

Emii Khaos Over a year ago

No, as the last rule under access_control forces every access to every other location to have the ROLE_USER role, which only authenticated users can have.

Wing · Accepted Answer · 2013-08-05 14:15:14Z

0

app/config/security.yml

secured_area:
    pattern:    ^/
    form_login:
        login_path: login  #this is routing name
        check_path: login_check  #this is routing name
    logout:
        path:   logout #this is routing name
        target: /

Edit

[1] you can try delete this:

auth_area:
    pattern:    ^/auth/(login|login_check)
    anonymous:  ~

[2] your path better that:

 <form action="{{ path('login_check') }}" method="POST">

Edit

It is example for login

firewalls:
    dev:
        pattern:  ^/(_(profiler|wdt)|css|images|js)/
        security: false
    secured_area:
        pattern:    ^/
        anonymous: ~
        form_login:
            login_path:  login
            check_path:  login_check
            always_use_default_target_path: true
            default_target_path: /top
        logout:
            path:   /user_logout
            target: /

edited Aug 5, 2013 at 14:15

answered Aug 5, 2013 at 13:37

Wing

443 bronze badges

5 Comments

Wing Over a year ago

can you list you loginAction??

Jukurrpa Over a year ago

Removing auth_area causes a redirection loop as it makes authentication mandatory to access /auth/login, thus redirecting to the same URL. Thanks for the tip for the form action (although not solving the problem either).

Wing Over a year ago

It is my test example , hope it can help you

Jukurrpa Over a year ago

Not working either... Plus I don't want to allow any anonymous access to the site.

Wing Over a year ago

I do not know how about your firewalls is working ,you can try to set firewall "dev" 'security: true' to test that the firewall is working . if you also can see the tool bar , your firewall is not working

Jekis · Accepted Answer · 2013-11-04 14:28:15Z

0

routing.yml

login_check:
    pattern:  /login_check
    defaults: { _controller: AcmeUserBundle:Default:loginCheck }

DefaultController.php

public function loginCheckAction()
{
    return $this->redirect($this->generateUrl('login'));
}

answered Nov 4, 2013 at 14:28

Jekis

4,7762 gold badges40 silver badges44 bronze badges

Collectives™ on Stack Overflow

Symfony login unable to find controller for path login_check despite being behind firewall

3 Answers 3

2 Comments

5 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

2 Comments

5 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related