Page MenuHomePhabricator

SO878 Step 3: Finalize settings and user experience
Closed, ResolvedPublic

Description

Objective: The user experience using WebAuthn is smooth and seamless. Also, users can
enable and disable the method.
The following functions are the result of this project phase

  • User setting to enable WebAuthn
  • Integration of necessary form fields in login and registration form
  • Configuration variables on the server side to customize WebAuthn

Event Timeline

Change 527089 had a related patch set uploaded (by ItSpiderman; owner: ItSpiderman):
[mediawiki/extensions/OATHAuth@master] UI upgrade

https://gerrit.wikimedia.org/r/527089

Screenshot 2019-08-07 at 09.53.41.png (1×2 px, 234 KB)

^ to show the re-introduction of the empty "available" section. And below is how it currently is in master

Screenshot 2019-08-07 at 10.02.26.png (532×2 px, 110 KB)

As mentioned in T226056 too... I wonder if we should have some sort of non technical/"laymans" description?

And I guess in the totp case... Some sort of mobile app suggestion/recommendations?

FB/Google examples:

Screenshot 2019-08-07 at 10.06.29.png (976×1 px, 180 KB)

Screenshot 2019-08-07 at 10.08.49.png (852×1 px, 111 KB)

Screenshot 2019-08-07 at 10.10.15.png (284×1 px, 59 KB)

Re-introduction of empty "Available methods" section is now fixed

One minor niggle, but I'm guesing it's due to the existence of the button and the text... Is that "TOTP (one-time token)" is slightly higher than "Two-factor authentication:"

Not going to block the merge on it though

Change 527089 merged by jenkins-bot:
[mediawiki/extensions/OATHAuth@master] UI upgrade

https://gerrit.wikimedia.org/r/527089

I like this improvement a lot ! The messages do indeed still need some work.

I was looking at the screenshot of FB by Reedy and was wondering if we too should consider making the recovery codes a separate method ? Might make more sense.

I like this improvement a lot ! The messages do indeed still need some work.

Patches welcome ;)

I was looking at the screenshot of FB by Reedy and was wondering if we too should consider making the recovery codes a separate method ? Might make more sense.

Could be an interesting thing to do. Because the WebAuthn method technically has no recovery method... Beyond allowing multiple devices/keys

Seems worth filing it as a separate task, as it's possibly out of scope for this