Bug 207821
| Summary: | Support FIDO2 Security Keys with PIN | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Pedro Tôrres <t0rr3sp3dr0> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | jiewen_tan, t0rr3sp3dr0 |
| Priority: | P2 | ||
| Version: | Safari 13 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Pedro Tôrres
Currently Safari doesn't ask for a PIN on security keys that have it set, this causes userVerification never to be true when invoking `navigator.credentials.get`.
Newer security keys require the PIN to be entered even if userVerification is set to discouraged, these keys cannot be used on Safari at all is a PIN has already been set. If the PIN has not already been set, then the security keys works with reduced capabilities, resident keys are not supported on this operation mode.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Jiewen Tan
*** This bug has been marked as a duplicate of bug 191516 ***