mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-08 03:09:39 +03:00
User cannot login after enabling MFA #2813
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @hanserasmus on GitHub (May 25, 2022).
Attempted Debugging
Searched GitHub Issues
Describe the Scenario
I am feeling really stupid as I cannot solve this. I am setting up as a test a central privacyIDEA server to see how MFA works. In the process I downloaded their app as well. I went into my Bookstack APP of which the auth backend is LDAP, and enabled MFA for only my user under my user profile. I downloaded the backup codes as well. In the privacyIDEA app I scanned the QR code and used the generated PIN to test the login on the screen that was in front of me. It worked. But, stupidly, I logged out and tried to log back in, instead of opening a new browser and test there whilst keeping my current session live. Now I cannot log in.
I don't see any errors in the apache logs, and there is nothing in the laravel logs either.
Could anyone please point me to where I can look for more info or how I can just at least enable my login again (by disabling 2FA for my user)? I cannot put this instance into Debug mode as it is exposed to the internet at this time.
Exact BookStack Version
v22.03.1
Log Content
Apache access.log shows this:
Nothing in error.log and nothing in Laravel.log
PHP Version
PHP 7.4.3
Hosting Environment
Self hosted VMware VM with Ubuntu 20.04.3
@ssddanbrown commented on GitHub (May 25, 2022):
Hi @hanserasmus,
It's very rare that you'd see that screen but get nothing logged to the
laravel.logfile. Are you sure you're looking at the correct file? Does that file exist at all?In regards to resetting MFA, this can be done via the command line, See the "Reset User MFA Methods" section on this page:
https://www.bookstackapp.com/docs/admin/commands/
@hanserasmus commented on GitHub (May 26, 2022):
Hi @ssddanbrown As always you came to the rescue. I was indeed looking at the correct laravel.log. And the file was indeed there. But never realised the web user does not have write access to it. Changed it so that apache has write access, and all of a sudden MFA started working too. It seems the MFA process needed to write a log entry in there and was not able to. Checked the log now and found this stacktrace:
So not sure what is still the issue. At least I am able to log in again now. But this issue probably needs to get fixed on my side.
@ssddanbrown commented on GitHub (May 30, 2022):
Hi @hanserasmus,
No need to worry about the
StoppedAuthenticationExceptionin the log file. This is just part of the MFA interception flow. I've since opened #3468 to prevent this from being reported in the log, and have pushed a patch within16e023985dto be part of the next feature release. You can ignore this log lines until then.Since the core issue is solved I'll close this off.