Buy
Buy

With a Subscription, click any sentence in the script to jump to that part of the video!

Login Subscribe

Go back to the login page. I wonder what happens if we fail the login... which, is only possible right now if we use a non-existent email address. Oh!

Cannot redirect to an empty URL

Filling in getLogUrl()

Hmm: this is coming from AbstractFormLoginAuthenticator our authenticator's base class. If you dug a bit, you'd find out that, on failure, that authenticator class is calling getLoginUrl() and trying to redirect there. And, yea, that makes sense: if we fail login, the user should be redirected back to the login page. To make this actually work, all we need to do is fill in this method.

No problem: return $this->router->generate('app_login'):

... lines 1 - 13
class LoginFormAuthenticator extends AbstractFormLoginAuthenticator
{
... lines 16 - 55
protected function getLoginUrl()
{
return $this->router->generate('app_login');
}
}

Ok, try it again: refresh and... perfect! Hey! You can even see an error message on top:

Username could not be found.

We get that exact error because of where the authenticator fails: we failed to return a user from getUser():

... lines 1 - 13
class LoginFormAuthenticator extends AbstractFormLoginAuthenticator
{
... lines 16 - 39
public function getUser($credentials, UserProviderInterface $userProvider)
{
return $this->userRepository->findOneBy(['email' => $credentials['email']]);
}
... lines 44 - 59
}

In a little while, we'll learn how to customize this message because... probably saying "Email" could not be found would make more sense.

The other common place where your authenticator can fail is in the checkCredentials() method:

... lines 1 - 13
class LoginFormAuthenticator extends AbstractFormLoginAuthenticator
{
... lines 16 - 44
public function checkCredentials($credentials, UserInterface $user)
{
// only needed if we need to check a password - we'll do that later!
return true;
}
... lines 50 - 59
}

Try returning false here for a second:

// ...
    public function checkCredentials($credentials, UserInterface $user)
    {
        return false;
    }
// ...

Then, login with a legitimate user. Nice!

Invalid credentials.

Anyways, go change that back to true:

... lines 1 - 13
class LoginFormAuthenticator extends AbstractFormLoginAuthenticator
{
... lines 16 - 44
public function checkCredentials($credentials, UserInterface $user)
{
// only needed if we need to check a password - we'll do that later!
return true;
}
... lines 50 - 59
}

How Authentication Errors are Stored

What I really want to find out is: where are these errors coming from? In SecurityController, we're getting the error by calling some $authenticationUtils->getLastAuthenticationError() method:

... lines 1 - 6
use Symfony\Component\Security\Http\Authentication\AuthenticationUtils;
class SecurityController extends AbstractController
{
... lines 11 - 13
public function login(AuthenticationUtils $authenticationUtils)
{
// get the login error if there is one
$error = $authenticationUtils->getLastAuthenticationError();
... lines 18 - 21
return $this->render('security/login.html.twig', [
... line 23
'error' => $error,
]);
}
}

We're passing that into the template and rendering its messageKey property... with some translation magic we'll talk about soon too:

... lines 1 - 10
{% block body %}
<form class="form-signin" method="post">
{% if error %}
<div class="alert alert-danger">{{ error.messageKey|trans(error.messageData, 'security') }}</div>
{% endif %}
... lines 16 - 29
</form>
{% endblock %}

The point is: we magically fetch the "error" from... somewhere and render it. Let's demystify that. Go back to the top of your authenticator and hold command or control to click into AbstractFormLoginAuthenticator.

In reality, when authentication fails, this onAuthenticationFailure() method is called. It's a bit technical, but when authentication fails, internally, it's because something threw an AuthenticationException, which is passed to this method. And, ah: this method stores that exception onto a special key in the session! Then, back in the controller, the lastAuthenticationError() method is just a shortcut to read that key off of the session!

So, it's simple: our authenticator stores the error in the session and then we read the error from the session in our controller and render it:

... lines 1 - 8
class SecurityController extends AbstractController
{
... lines 11 - 13
public function login(AuthenticationUtils $authenticationUtils)
{
// get the login error if there is one
$error = $authenticationUtils->getLastAuthenticationError();
... lines 18 - 25
}
}

The last thing onAuthenticationFailure() does is call our getLoginUrl() method and redirect there.

Filling in the Last Email

Go back to the login form and fail authentication again with a fake email. We see the error... but the email field is empty - that's not ideal. For convenience, it should pre-fill with the email I just entered.

Look at the controller again. Hmm: we are calling a getLastUsername() method and passing that into the template:

... lines 1 - 10
{% block body %}
<form class="form-signin" method="post">
... lines 13 - 18
<input type="email" name="email" id="inputEmail" class="form-control" placeholder="Email address" required autofocus>
... lines 20 - 29
</form>
{% endblock %}

Oh, but I forgot to render it! Add value= and print last_username:

... lines 1 - 10
{% block body %}
<form class="form-signin" method="post">
... lines 13 - 18
<input type="email" value="{{ last_username }}" name="email" id="inputEmail" class="form-control" placeholder="Email address" required autofocus>
... lines 20 - 29
</form>
{% endblock %}

But... we're not quite done. Unlike the error message, the last user name is not automatically stored to the session. This is something that we need to do inside of our LoginFormAuthenticator. But, it's super easy. Inside getCredentials(), instead of returning, add $credentials = :

... lines 1 - 14
class LoginFormAuthenticator extends AbstractFormLoginAuthenticator
{
... lines 17 - 32
public function getCredentials(Request $request)
{
$credentials = [
'email' => $request->request->get('email'),
'password' => $request->request->get('password'),
];
... lines 39 - 45
}
... lines 47 - 67
}

Now, set the email onto the session with $request->getSession()->set(). Use a special key: Security - the one from the Security component - ::LAST_USERNAME and set this to $credentials['email']:

... lines 1 - 14
class LoginFormAuthenticator extends AbstractFormLoginAuthenticator
{
... lines 17 - 32
public function getCredentials(Request $request)
{
$credentials = [
'email' => $request->request->get('email'),
'password' => $request->request->get('password'),
];
$request->getSession()->set(
Security::LAST_USERNAME,
$credentials['email']
);
... lines 44 - 45
}
... lines 47 - 67
}

Then, at the bottom, return $credentials:

... lines 1 - 14
class LoginFormAuthenticator extends AbstractFormLoginAuthenticator
{
... lines 17 - 32
public function getCredentials(Request $request)
{
$credentials = [
'email' => $request->request->get('email'),
'password' => $request->request->get('password'),
];
$request->getSession()->set(
Security::LAST_USERNAME,
$credentials['email']
);
return $credentials;
}
... lines 47 - 67
}

Try it! Go back, login with that same email address and... nice! Both the error and the last email are read from the session and displayed.

Next: let's learn how to customize these error messages. And, we really need a way to logout.

Leave a comment!

  • 2019-02-05 bahae

    very grateful! Thank you!

  • 2019-02-05 weaverryan

    Hey bahae!

    Nice work! Yes, the AbstractFormLoginAuthenticator class that your authenticator extends implements the onAuthenticationFailure() method and IT is responsible for taking the error and putting it onto the session so that it's accessible via the error.messageKey. So, your solution was perfect - you were overriding this functionality on accident - but you definitely want it :).

    Cheers!

  • 2019-02-02 bahae

    Hi again friends,
    i find the solution of this dummy problem, when i generated my LoginFormAuthenticator, the console generate lot of methods like [supports(),getCredentials(),...] one of them named (onAuthenticationFailure()) this is the problem !! delete it and everything works great.
    Cheers! XD

  • 2019-02-02 bahae

    Hi friends,
    first of all I want to say thanks for this great and very helpful work!!
    My problem is i can't find the error message when i try to login with a false email. even if my template have "error.messageKey", and my controller have also rendered the "error" key!
    any solution for that?

  • 2019-01-14 weaverryan

    Hey OutspOaken!

    Hmm, that's a bit misleading. If you've configured your app to have a session (which is the default in a new application thanks to this line in the recipe: https://github.com/symfony/... then you don't need to worry about this. What changed is that, until now, if you did NOT have a session configured, calling $request->getSession() was allowed, but it would return null. In Symfony 5, instead of returning null, it will throw an exception.

    So, if you know that your app uses a session, you're fine to just se things directly on the session. But if you were building some re-usable bundle, you would want to check first that the session exists.

    Cheers!

  • 2019-01-14 OutspOaken

    It seems we have to check if a session exists before getting it since Symfony 4.1:
    https://symfony.com/blog/ne...

    So, to set the email onto the session, we have to do:
    if ($request->hasSession() && ($session = $request->getSession())) {
    $session->set(Security::LAST_USERNAME, $credentials['email']);
    }

    Is that correct ?

  • 2018-09-19 Axel Verdruye

    thanks! No its fine :) I'll rewatch the videos. Always good to refresh the memory. ty for the response. Great tutorials btw !

  • 2018-09-17 Victor Bocharsky

    Hey Axel,

    We count progress on video watching, so it's impossible to get a certificate for an unfinished course, since since it does not have all the videos. Moreover, the chapters that are not released yet is just a draft, that can be changed. But yeah, most of the time it does not change or we do very minor changes in it. So, if you won't want to watch the new videos when they are released - ping us again when this course is completely released and we'll give you the certificate.

    Cheers!

  • 2018-09-17 Axel Verdruye

    Hi, im completing the course without the videos (as they are not yet implemented). But how do i complete the certificate? As the course % depends on the amount of videos you viewed.

    Thanks !