Vui

Maybe it is because the route error? Have you try it in postman or insomnia?

> With the new Symfony authenticator-based security system, we are probably going to move most of the config to per-firewall configuration (with a `lexik_jwt: ~` configurable authenticator). Would that fit...

Is the bug still exist? How can we reproduce the bug?

> {"code":401,"message":{"meta":{"code":401,"status":"error","message":"Bad credentials, please verify that your username\/password are correctly set."}}} Yea because `JWTAuthenticationFailureResponse` constructor first argument is `message` and it will replace the default message in that class. If...

> This error is showed me but I don't know why. > > I correctly provide the username and the password but it doesn't work. Do you mean this error...

> In case this is still happening to someone, it may be because in the user checker, you need to throw a new AuthenticationException to trigger failure_handler event. > >...

Perhaps you need custom authenticator or refer here https://github.com/lexik/LexikJWTAuthenticationBundle/blob/2.x/Resources/doc/2-data-customization.md

> This seems related to preloading. I started getting this recently after some upgrades, and I disabled preloading temporarily until I figured out what's going on. > > The issue...

> The symfony security system is all about a User object (see its UserInterface and TokenInterface), you can't use it to perform authentication/authorization without such object. +1 > I think...

Now you may use `php bin/console lexik:jwt:generate-keypair` to generate key without worrying anything.