Unable to find the controller for path "/api/login_check" Again

[agatumm420]

I've encountered the same problem earlier but fix from the issue [] (#1014) helped (i deleted ^ in fornt of api in security.yaml). Now the problem is back and nothing seems to help
security.yaml
`

security:
    enable_authenticator_manager: true
  
    password_hashers:
        Symfony\Component\Security\Core\User\PasswordAuthenticatedUserInterface: 'auto'
    
    providers:
        
        app_user_provider:
            entity:
                class: App\Entity\User
                property: email

    firewalls:
        login:
            pattern: /api/login
            stateless: true
            provider: app_user_provider
            json_login:
                username_path: email
              
                check_path: api_login_check # or api_login_check as defined in config/routes.yaml
                success_handler: lexik_jwt_authentication.handler.authentication_success
                failure_handler: lexik_jwt_authentication.handler.authentication_failure
        api:
            pattern: /api
            stateless: true

            jwt:
                authenticator: app.custom_authenticator

    access_control:
     


         - { path: /api,       roles: PUBLIC_ACCESS}

         - {path: /api/login_check, roles: PUBLIC_ACCESS}

routes.yaml

controllers:
    resource: ../src/Controller/
    type: attribute
kernel:
    resource: ../src/Kernel.php
    type: annotation
api_login_check:
    path: api/login_check

`
I'll be greatfull for any direction, at this point I feel like I've run out of options.

[agatumm420]

@chalasr Why was my issue moved here?

[danielrhodeswarp]

Hello @agatumm420 I'm also really struggling with this "unable to find the controller" / 404 error.
I know I can do things manually, but I want to avoid that as I want to put another security package over the top of Lexik (Scheb 2FA).
Did you get any good solutions to this?
One thing I've noticed in your security.yaml above is that your /api and /api/login_check are both "PUBLIC_ACCESS" - I wonder if that is causing the issue in your scenario?

[oriiyx]

Hey @danielrhodeswarp - sorry to hijack this thread - but did you successfully implement 2FA over Lexik? I'm having hard trouble with this integration and could use some help if you'd be willing to spare a few minutes? Cheers :)

[danielrhodeswarp]

Hello @oriiyx Yes I did get Scheb 2Fa working over Lexik in the end - it was mostly about double-checking the configurations and reading documentation. But with a lot of trial-and-error and experimenting too.

These documents helped generally:
[] For Lexik: https://symfony.com/bundles/LexikJWTAuthenticationBundle/current/index.html

[] For Scheb 2FA: https://symfony.com/bundles/SchebTwoFactorBundle/current/index.html (especially https://symfony.com/bundles/SchebTwoFactorBundle/current/api.html)

My biggest headache was:
[] I had to make the login routes for Lexik be stateless: false which uses traditional cookies - these cookies will need to be caught (and resent) by some of your front-end's API calls.

Happy to help where I can - are you having trouble with Lexik itself or the 2FA on top of Lexik?

[danielrhodeswarp]

Not sure if this helps, but:

I've noticed that omitting "success_handler" in security.yaml results in the [Unable to find the controller for path "/login_check". The route is wrongly configured.] error (when you /login_check with correct credentials for a user).

Which, by extension, means that a customised - and broken - success handler could also give this error.

Omitting failure_handler doesn't generate any errors (when you /login_check with incorrect credentials for a user) - it's simply a slightly different JSON response to the default failure handler.

[adp1002]

Are you sending the request with the Content-Type: application/json header?

[Griffin641498]

I've encountered the same problem earlier but fix from the issue [] (#1014) helped (i deleted ^ in fornt of api in security.yaml). Now the problem is back and nothing seems to help
security.yaml
`

security:
    enable_authenticator_manager: true
  
    password_hashers:
        Symfony\Component\Security\Core\User\PasswordAuthenticatedUserInterface: 'auto'
    
    providers:
        
        app_user_provider:
            entity:
                class: App\Entity\User
                property: email

    firewalls:
        login:
            pattern: /api/login
            stateless: true
            provider: app_user_provider
            json_login:
                username_path: email
              
                check_path: api_login_check # or api_login_check as defined in config/routes.yaml
                success_handler: lexik_jwt_authentication.handler.authentication_success
                failure_handler: lexik_jwt_authentication.handler.authentication_failure
        api:
            pattern: /api
            stateless: true

            jwt:
                authenticator: app.custom_authenticator

    access_control:
     


         - { path: /api,       roles: PUBLIC_ACCESS}

         - {path: /api/login_check, roles: PUBLIC_ACCESS}

routes.yaml

controllers:
    resource: ../src/Controller/
    type: attribute
kernel:
    resource: ../src/Kernel.php
    type: annotation
api_login_check:
    path: api/login_check

`
I'll be greatfull for any direction, at this point I feel like I've run out of options.

[Steve-3d]

Although this is over 1 year old, in case anybody else has the same problem and finds this issue: I solved it by replacing the "check_path: api_login_check" with the real URL: e.g. "check_path: /api/login" - but you still need to define this route in the routes.yaml as mentioned in the Docs.

[mateusfmello]

To avoid the 404 error, it is necessary to inform the access data and with the header Content-Type: application/json