[Webkit-unassigned] [Bug 213642] New: [WebAuthn] Client PIN flow does not indicate that a final authenticator touch is needed
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Jun 26 02:46:31 PDT 2020
https://bugs.webkit.org/show_bug.cgi?id=213642
Bug ID: 213642
Summary: [WebAuthn] Client PIN flow does not indicate that a
final authenticator touch is needed
Product: WebKit
Version: Safari Technology Preview
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: WebCore Misc.
Assignee: webkit-unassigned at lists.webkit.org
Reporter: eirbjo at gmail.com
Congratulations with the new Client PIN support in Safari!
When testing this with Safari Technology Preview 109, I noticed that the client PIN flow ends without any indication to the user that a final authenticator touch is needed to complete the operation.
Observation:
1: The user initiates authentication
2: The "Do you want to sign in .. using a security key" dialog appears, telling the user to insert a key and to activate it
3: The user touches the security key to select it
4: The "Enter a PIN to unlock this authenticator" dialog appears
5: The user enters a valid PIN, clicks "Submit"
6: The PIN entry dialog disappears and the security key starts blinking, but the client UX has no indication that the user must touch the authenticator again to complete the operation
This could be improved by adding some form of dialog after step 5 to indicate that the operation is not done before the user touches/activates the authenticator.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20200626/82fead45/attachment.htm>
More information about the webkit-unassigned
mailing list