@@ -333,7 +333,7 @@ Finally, configure your ``firewalls`` key in ``security.yml`` to use this authen
333
333
'logout' => true,
334
334
'guard' => [
335
335
'authenticators' => [
336
- TokenAuthenticator::class
336
+ TokenAuthenticator::class,
337
337
],
338
338
],
339
339
// ...
@@ -419,7 +419,7 @@ Each authenticator needs the following methods:
419
419
the user authenticate (e.g. a 401 response that says "token is missing!").
420
420
421
421
**supportsRememberMe() **
422
- If you want to support "remember me" functionality, return true from this method.
422
+ If you want to support "remember me" functionality, return `` true `` from this method.
423
423
You will still need to activate ``remember_me `` under your firewall for it to work.
424
424
Since this is a stateless API, you do not want to support "remember me"
425
425
functionality in this example.
@@ -428,7 +428,8 @@ Each authenticator needs the following methods:
428
428
If you are implementing the :class: `Symfony\\ Component\\ Security\\ Guard\\ AuthenticatorInterface `
429
429
instead of extending the :class: `Symfony\\ Component\\ Security\\ Guard\\ AbstractGuardAuthenticator `
430
430
class, you have to implement this method. It will be called
431
- after a successful authentication to create and return the token
431
+ after a successful authentication to create and return the token (a
432
+ class implementing :class: `Symfony\\ Component\\ Security\\ Guard\\ Token\\ GuardTokenInterface `)
432
433
for the user, who was supplied as the first argument.
433
434
434
435
The picture below shows how Symfony calls Guard Authenticator methods:
0 commit comments