See parent task for details.
Description
Description
Event Timeline
Comment Actions
Test plan:
- password login
- captcha
- OATH 2FA
- WebAuthn 2FA
- user account creation
- login via action=clientlogin
- bot login via action=login
- central login / autologin / edge login
- logout
- using an OAuth 1 consumer with HMAC signature
- using an OAuth 1 consumer with RSA signature
- using an OAuth 2 consumer
- creating and using a new OAuth 1 owner-only consumer
- creating and using a new OAuth 2 owner-only consumer
All works as expected, except WebAuthn which apparently cannot be set up without steward involvement (cf T379433). I'll test that sometime later.
Comment Actions
Should the 2FA testing be split off into a different task (presumably one that doesn't block T379986 given that's been declared Resolved) and this one marked done?
Comment Actions
I don't think the PHP 8 rollout should be blocked on the remainder of this task, if that's what you mean - the WebAuthn userbase is tiny. If you feel the task being open is confusing, feel free to close it.
Comment Actions
We tested WebAuthn extensively during the SUL3 rollout. The results are, uh, mixed... but none of the problems have anything to do with the PHP version.