Bug 217050
| Summary: | [WebAuthn] Do WebAuthn(U2F) registration through https://myaccount.google.com/ doesn't block registered security keys | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | nuno.sung <nuno.sung> |
| Component: | WebKit Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | agektmr, jiewen_tan, jond, webkit-bug-importer, webkit-unassigned |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari Technology Preview | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
nuno.sung
Test STP 113 on macOS 10.15.6
1. Open URL https://myaccount.google.com/ and then go to 2-Step Verification to add security key.
2. Use security key through USB transports
3. Security key receive U2F_REG command and success to add this key.
4. Click "add security key" again with the same key.
5. The same key is still allowed to registered with error.
On Chrome v85 on the same MAC machine and Chromes on Windows10, the website's error dialog "Security Key already registered" will be showed up in this case.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Jiewen Tan
*** This bug has been marked as a duplicate of bug 203200 ***