Since wikitech will soon stop providing 2fa validation, we need to use idm as the totp provider instead.
Description
Details
| Subject | Author | Repo | Branch | Lines +/- | |
|---|---|---|---|---|---|
| auth: Properly remove 2FA support | Majavah | labs/striker | master | +3 -419 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T189531 All Wikimedia developer services should use single sign-on | |||
| Resolved | None | T161859 Make Wikitech an SUL wiki | |||
| Duplicate | None | T359551 Replace wikitech as source of two-factor auth protection for developer accounts | |||
| Declined | None | T373461 Striker: use idm for 2fa validation instead of wikitech |
Event Timeline
Simon writes:
I’ve deploy the new 2FA implementation to idm-test.wikimedia.org. If you sign in, you should see a button labeled "Manage two factor authentication”. If you click that you’ll be guided though setting up 2FA for your account. It’s not currently connected to anything, so enabling it will not break or influence your actual 2FA anywhere.
Example:
import requests
headers = {'Authorization': 'Token 54ba5ed5eec4d6a5931f20e9e849be6fe410cfbd', 'Content-Type': 'application/json’}
url = 'https://idm-test.wikimedia.org/mediawiki/api/totp/'
payload = {'user': 'slyngshede', 'token': '123456’}
r = requests.post(headers=headers, json=payload, url=url)This will return a JSON object. e.g. {"user":"slyngshede","valid":false,"enabled":false}
User is just echoing the username you provided in the post, valid indicates if the 2FA token is accepted and enabled tells you is the user has 2FA enabled or not.
I figured that might be hand to signal to the user that they need to enable 2FA.
I'm definitely going in circles here, but @bd808 suggests that we just skip ahead to https://phabricator.wikimedia.org/T359554 and let striker run without 2fa until 2fa is enabled in CAS. That would at least stop me being confused about what the intermediate steps are in all this.
I'm not quite ready to close this as invalid but I'm dropping the priority since we are probably not doing it!
Change #1077444 had a related patch set uploaded (by Majavah; author: Majavah):
[labs/striker@master] auth: Properly remove OATHAuth support
Change #1077444 merged by jenkins-bot:
[labs/striker@master] auth: Properly remove 2FA support