Please take the added complexity and combinations seriously. App developers need to update their testing procedures to test all the combinations of login appro

Please take the added complexity and combinations seriously. App developers need to update their testing procedures to test all the combinations of login approaches over many different implementations (browsers, operating systems, hardware tokens, local vs remote, etc). The traditional username, password flow could be tested once and work nearly everywhere. As an example, I’ve been helping QA a webauthn issue on Wikipedia, that leads to potential account lock-out, due to passkeys not getting published to the various wiki sites completely. encountered <https://phabricator.wikimedia.org/T358771 https://phabricator.wikimedia.org/T358771> Fewer than 100 Wikipedia editors use webauthn , so the issue doesn’t receive much attention. When implementing webauthn, QA testing , customer telemetry, customer onboarding & customer support all need much more investment to provide the same level of service.