Skip to content

Commit f1540ee

Browse files
committed
Update troubleshooting
1 parent efd7991 commit f1540ee

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
@@ -246,8 +246,8 @@ Troubleshooting
246246
No
247247
Unknown issue. Try to reach out for help by `creating an issue`_ and let us know what you've already tested.
248248

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

252252
Yes
253253
Continue with 4)
@@ -257,24 +257,29 @@ Troubleshooting
257257
us know what you've already tested.
258258

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

262262
Yes, it's called
263263
Continue with 5)
264264

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

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

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

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

280285
Trusted device cookie is not set

0 commit comments

Comments
 (0)