More form_login Config

Hey Mahmut,

I didn't get why you send 2 different codes from onAuthenticationSuccess().. .which is yours? I suppose you use the custom authenticator like that first code block, so I will assume that's your code. Maybe try to debug the flow with dd()? Make sure you hit that return new RedirectResponse($this->router->generate('app_main_homepage',['username' => $username])); line on the successful login. If not - most probably you hit the earlier redirect which is return new RedirectResponse($target);. Probably you need to tweak the logic in your onAuthenticationSuccess() to make sure you redirect users to correct pages.

I hope that helps!

Cheers!

Hi Victor,

Sorry for confusing. I am using below code during error. I mean if ı use built-in authenticator, it is redirecting same login page.

However, my custom login authenticator is working well.

    public function onAuthenticationSuccess(Request $request, TokenInterface $token, string $firewallName): ?Response
    {
        return $this->successHandler->onAuthenticationSuccess($request, $token);
    }

Hey Mahmut,

The built-in authenticator can be configured via the configuration, but if you need more flexibility - better to go with your own custom authenticator where you can do whatever you want. Still you can debug the flow using dd() - that should help to understand the flow and why it does not work as expected for you.

Cheers!

Hey Francois,

You can totally ignore that value={{ last_username }} of course if it's not something you need. But the idea behind this thing is to keep the last username user entered - useful when they have misprint their credentials, e.g. password so they don't need to retype the username again and try a different password. That's a common practice on may websites over the internet, but that's totally up to you. Of course when you log out going to the /logout URL - the session will be destroyed and you will not see that last_username anymore.

Cheers!

Hey @Soufiyane!

Are you referring to how to print the "last username" thing? If so, the 2 steps are:

1) In your custom authenticator, in authenticate(), after reading the email, call:

$request->getSession()->set(SecurityRequestAttributes::LAST_USERNAME, $credentials['username']);

2) In your controller, read that value in the same way as see in this chapter :).

Let me know if that helps!

Cheers!

Hey Leszek,

You only need to inject the service Symfony\Component\Security\Http\Authentication\AuthenticationUtils into your Controller's method, or in case you need it in your authenticator, you can add another argument constructor and inject it there

Cheers!