Page MenuHomePhabricator

2FA broken on
Closed, ResolvedPublic


Possibly other WMF wikis too, but every time I try to input the TOTP code in, I get the error message that it failed to validate two-factor credentials. I was able to get in with a remembered account on a different browser and disable 2FA using a scratch code. Attempting to re-enable 2FA results in the same message on the screen that has me enter a code to validate.

I've verified using both my regular app as well as a separate library on a separate device that the codes I'm typing in are correct. Can you please investigate why the server-side is believing the codes are wrong? My initial guess is a badly-synced clock on the server.

Feel free to poke me in freenode IRC MediaWiki-General (nick: Skizzerz) and I can help troubleshoot things further on my end as well.

Related Objects


Event Timeline

Skizzerz created this task.Apr 17 2019, 4:03 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 17 2019, 4:03 PM
Skizzerz updated the task description. (Show Details)Apr 17 2019, 4:04 PM

@Skizzerz: Is the clock on your device accurate?

Krenair triaged this task as Unbreak Now! priority.Apr 17 2019, 4:07 PM

Oh, yeah, broken for me too.

Restricted Application added subscribers: Liuxinyu970226, TerraCodes. · View Herald TranscriptApr 17 2019, 4:07 PM

I can log in just fine on enwiki but not mediawiki. Marking as possible deployment blocker for 1.34.0-wmf.1

I've tried two different devices and two different libraries. Checking my PC clock (one of the devices tested), it's about 1.5 seconds behind what the website lists as the current time.

Given that TOTP gives you at minimum 30 seconds, this seems like it shouldn't cause issues.

Isarra added a subscriber: Isarra.Apr 17 2019, 4:10 PM

Can confirm, broken on

Given other wikis don't have the same deployment out and still work we can probably login via the rest and have centralauth carry it over for now, but this seems kind of not good.

Krenair added subscribers: Reedy, Jdforrester-WMF.EditedApr 17 2019, 4:17 PM

According to there's 4 OATHAuth changes in this deployment, of which these two sound more likely to be involved:

Edit: @Skizzerz pointed out to me, probably not the latter as we're using TOTP not HOTP?

Change 504614 had a related patch set uploaded (by Jforrester; owner: Reedy):
[mediawiki/extensions/OATHAuth@wmf/1.34.0-wmf.1] Revert "Replace hotp.php with composer library"

Change 504614 merged by jenkins-bot:
[mediawiki/extensions/OATHAuth@wmf/1.34.0-wmf.1] Revert "Replace hotp.php with composer library"

Mentioned in SAL (#wikimedia-operations) [2019-04-17T17:18:30Z] <jforrester@deploy1001> Synchronized php-1.34.0-wmf.1/extensions/OATHAuth/: UBN T221257 train un-blocker (duration: 01m 02s)

Patch reverted in wmf.1 (but not master); this should unblock the train for now.

Change 504657 had a related patch set uploaded (by Reedy; owner: Reedy):
[mediawiki/extensions/OATHAuth@master] Update jakobo/hotp-php to v1.0.1

Change 504657 merged by jenkins-bot:
[mediawiki/extensions/OATHAuth@master] Update jakobo/hotp-php to v1.0.1

Jdforrester-WMF closed this task as Resolved.Apr 17 2019, 8:59 PM
Jdforrester-WMF assigned this task to Reedy.

OK, this should now be fixed. Hopefully.