Skip to content

Commit fc944c6

Browse files
committed
Update troubleshooting
1 parent f666f9f commit fc944c6

File tree

1 file changed

+13
-8
lines changed

1 file changed

+13
-8
lines changed

doc/troubleshooting.rst

Lines changed: 13 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -236,8 +236,8 @@ Troubleshooting
236236
No
237237
Unknown issue. Try to reach out for help by `creating an issue`_ and let us know what you've already tested.
238238

239-
#. On login, do you reach the end (return statement) of method
240-
``Scheb\TwoFactorBundle\Security\Authentication\Provider\AuthenticationProviderDecorator::authenticate()``?
239+
#. On login, do you reach the start of method
240+
``Scheb\TwoFactorBundle\Security\TwoFactor\Event\AuthenticationTokenListener::onAuthenticationTokenCreated()``?
241241

242242
Yes
243243
Continue with 4)
@@ -247,24 +247,29 @@ Troubleshooting
247247
us know what you've already tested.
248248

249249
#. On login, is method
250-
``Scheb\TwoFactorBundle\Security\TwoFactor\Handler\TwoFactorProviderInitiator::getActiveTwoFactorProviders()`` called?
250+
``Scheb\TwoFactorBundle\Security\TwoFactor\Provider\TwoFactorProviderInitiator::beginTwoFactorAuthentication()`` called?
251251

252252
Yes, it's called
253253
Continue with 5)
254254

255255
No it's not called
256-
**Solution:** Two-factor authentication is skipped, either because of the IP whitelist or because of a trusted
257-
device token. IP whitelist is part of the bundle's configuration. Maybe you have whitelisted "localhost" or
258-
"127.0.0.1"? The trusted device cookie can be removed with your browser's developer tools.
256+
**Solution:** Two-factor authentication is skipped for some reason. To find out what's going on, check what is
257+
happening in ``Scheb\TwoFactorBundle\Security\TwoFactor\Provider\TwoFactorProviderInitiator::beginTwoFactorAuthentication()``
258+
before the call to the ``beginTwoFactorAuthentication()`` method. It's typically one of the reasons:
259259

260-
#. Does ``Scheb\TwoFactorBundle\Security\TwoFactor\Handler\TwoFactorProviderInitiator::getActiveTwoFactorProviders()``
260+
* The security token class used by the login method was not configured in the ``security_tokens``
261+
* Your IP is whitelisted. Maybe you have whitelisted "localhost" or "127.0.0.1" in the bundle configuration?
262+
* A trusted device cookie is set. The trusted device cookie can be removed with your browser's developer tools.
263+
* You have implemented a custom condition for 2fa, which skips 2fa.
264+
265+
#. Does ``\Scheb\TwoFactorBundle\Security\TwoFactor\Provider\TwoFactorProviderInitiator::getActiveTwoFactorProviders()``
261266
return any values?
262267

263268
Yes, it returns an array of strings
264269
Unknown issue. Try to reach out for help by `creating an issue`_ and let us know what you've already tested.
265270

266271
No, it returns an empty array
267-
**Solution:** our user doesn't have an active two-factor authentication method. Either the ``is*Enabled`` method
272+
**Solution:** your user doesn't have an active two-factor authentication method. Either the ``is*Enabled`` method
268273
returns ``false`` or an essential piece of data (e.g. Google Authenticator secret) is missing.
269274

270275
Trusted device cookie is not set

0 commit comments

Comments
 (0)