Using TFA 2.0-beta3 and TFA Basic Plugins 1.0-dev, I get a blank maintenance mode screen after i enter my user name and password, when I should have been offered to enter the TFA code. The TFA configuration is set to be optional, so I can actually (succesfully) log in with other accounts that dont have TFA enabled, but not with accounts that have TFA TOTP enabled.
Once I use another admin to put the site out of maintenance mode, and then change the cookie session back to the user having TFA problems, I just need to refresh that page (I am _not_ prompted to enter the login credentials again (good)) to get it to display as expected. Then I get to enter the TFA code and successfully log in.
Unsure if this is related to TFA or TFA Basic plugins.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | allow-to-use-tfa-in-maintenance-mode-2694723-5.patch | 785 bytes | rickj |
Comments
Comment #2
junaidpvWe also facing this issue. So, I worked on and prepared a patch to fix this. Here is the patch.
It brings a permission "Use TFA in maintenance mode", roles having this permission can use TFA in maintenance mode.
Comment #3
nullkernel commentedThanks for the patch. It worked for me. I'd say RTBC except that I believe the newly defined permission seems redundant, so I'm attaching an updated patch for review.
Drupal core defines a permission "Use the site in maintenance mode". I think that this permission should be reused, rather than a new one defined. I generally like customizability, but in this case I think:
I'm attaching an updated patch and interdiff.
Comment #4
jonas139 commentedI was having the same problem but the patch did the trick!
Thanks guys!
+1
Comment #5
rickj commentedI've just tripped over this. My site is set up with TFA mandatory for all admin accounts, and I got locked out due to a backup cron job hanging. I had to hack index.php to get back in - real pain!
I've updated the patch to match the latest release (line-number change), and marked RTBC. Could this be committed please?
Comment #6
francewhoaThis is to confirm that RickJ's patch resolves this challenge
Thanks to all contributors for resolving this
Could this patch be committed, please?
Comment #7
francewhoaFor those facing this challenge, the steps below allows you to temporarily log in your Drupal without any patch and without hacking Drupal:
Steps:
Keep in mind that, in the future, after you log out, the challenge will be back. For a permanent resolution, you need to apply the appropriate patch above.
Comment #9
poker10 commentedCommitted this, thanks everyone who contributed!