Bug 1793657 - Cannot Add Google Account with Security Key
Summary: Cannot Add Google Account with Security Key
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: webkit2gtk3
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Michael Catanzaro
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1793682
TreeView+ depends on / blocked
 
Reported: 2020-01-21 18:46 UTC by Michael Boisvert
Modified: 2020-06-01 18:58 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1793682 (view as bug list)
Environment:
Last Closed: 2020-06-01 18:58:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Security Key Denial Message (365.19 KB, image/png)
2020-01-21 18:46 UTC, Michael Boisvert
no flags Details


Links
System ID Private Priority Status Summary Last Updated
WebKit Project 205350 0 None None None 2020-06-01 18:58:03 UTC

Description Michael Boisvert 2020-01-21 18:46:22 UTC
Created attachment 1654371 [details]
Security Key Denial Message

Description of problem: I cannot add my Google account to Fedora that is secured with 2-step authentication using a YubiKey. A pop-up says "This browser does not support security keys."

Steps to Reproduce:
1. Fedora Settings -> Online Accounts -> Google
2. Input username and password
3. See pop-up.

Actual results: No way to add Google account that has 2-step authentication.

Expected results: You're able to use the YubiKey as 2-step authentication.

See screenshot.

Comment 1 Ben Cotton 2020-04-30 20:32:14 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2020-05-26 18:11:12 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Debarshi Ray 2020-06-01 18:44:18 UTC
I suspect that this bug is still relevant and should be re-opened. Michael?

Comment 4 Michael Catanzaro 2020-06-01 18:49:44 UTC
I think this is a request for Fido U2F or WebAuthn... not entirely sure what the difference between the two is. WebKitGTK does not support WebAuthn and I suspect there are no plans to implement. I think the cross-platform bits are in place, so probably only the Linux support is missing.

Comment 5 Debarshi Ray 2020-06-01 18:55:56 UTC
Ok, reopening and reassigning to webkit2gtk3.

Thanks for chiming in, mcatanzaro!

Comment 6 Michael Catanzaro 2020-06-01 18:58:04 UTC
Hm, no point in tracking this downstream. Upstream bug is https://bugs.webkit.org/show_bug.cgi?id=205350


Note You need to log in before you can comment on or make changes to this bug.