Skip to content

U2F support in the future versions of Chrome #423

Description

@dziudek

Hi,

Today I have seen in my JS console the following warning while I was logging in using my Yubikey:

The U2F Security Key API is deprecated and will be removed soon. If you own this website, please migrate to the Web Authentication API. For more information see https://groups.google.com/a/chromium.org/g/blink-dev/c/xHC3AtU_65A/m/yg20tsVFBAAJ

It means that in the next year security keys won't work at all with your plugin?

Activity

  1. innertruth commented on Nov 20, 2021

    @innertruth

    I don't get this message in the JS Console, I get a dialog for this message with the same text asking to block or give access. But issue 232 is I think a solution for this, maybe the maintainer can merge the code and 'bake' a new release.

  2. BackSeat commented on Nov 25, 2021

    @BackSeat

    I'm seeing this as a popup rather than in the JS console.

    Is this likely to be resolved before 1 February?

    Thanks.

  3. dziudek commented on Nov 25, 2021

    @dziudek
    Author

    @BackSeat - I can confirm - after latest Chrome update (v.96) I also get the notice about February 2022

  4. westonruter commented on Nov 29, 2021

    @westonruter
    Member

    I just got it as well:

    Screen Shot 2021-11-29 at 14 15 42
  5. blogtutor commented on Nov 30, 2021

    @blogtutor

    Is anyone on the plugin development team aware of this issue yet? Looks like it's going to be a big mess come February, if the plugin isn't changed over to the Web Authentication API by then.

  6. bemyhre commented on Nov 30, 2021

    @bemyhre

    This is an issue for me, as well. It sounds like this plugin will become useless for me in Feb. Even now, I cannot register my key on new things.

  7. timarney commented on Dec 6, 2021

    @timarney

    Noting a few folks have posted here here as well:
    https://wordpress.org/support/topic/u2f-api-deprecation-message/

  8. pjv commented on Dec 22, 2021

    @pjv
    Contributor

    Google documentation for the deprecation: https://groups.google.com/a/chromium.org/g/blink-dev/c/xHC3AtU_65A

    This will break logging in to wordpress for anyone using this plugin with a U2F security key in a chromium-based browser after February.

  9. supawiz6991 commented on Jan 11, 2022

    @supawiz6991

    Any update on this? We are currently 3 weeks from February...not knowing when the update will be hitting that will remove the U2F API means we could be in a real mess sooner than later.

  10. kasparsd commented on Jan 11, 2022

    @kasparsd
    Collaborator

    I personally haven't had time to work on this, unfortunately.

    The tricky thing is that the the two-factor plugin is currently available on both WP.org and Packagist.org which mirrors this source repo, however, adding webauthn will probably need some helper JS libraries to be added via npm (along with build tooling) so we'll need to either keep tracking the built assets as part of the repo or create a dedicated release repo which contains the built assets and map it to the Packagist source.

    Happy to support with reviewing a pull request if anyone is up for creating one.

    Relating this to #232.

  11. kasparsd commented on Jan 11, 2022

    @kasparsd
    Collaborator

    Here is some existing art from @mcguffin https://github.com/mcguffin/two-factor-webauthn

    Looks like we'll need to pull in both external JS and PHP dependencies (and potentially even PHP extensions) for this to work.

  12. added this to the 0.8.0 milestone on Jan 12, 2022
  13. mcguffin commented on Jan 21, 2022

    @mcguffin

    @kasparsd I'd be happy to craft a PR.

    I just managed to get rid of one of the large dependencies in mcguffin/two-factor-webauthn. The other ones are aesy to refactor. The PR should introduce about 2k new lines of PHP and 500 lines of JS.

    Minimum PHP would increase to 7.2 (according to phpcompatinfo), but luckily there are no other php extensions necessary as the ones WP requires anway.

  14. norbusan commented on Jan 21, 2022

    @norbusan

    Just FYI, since I am using Edge Beta I am already hit by the deprecation. I have added Wp-WebAuthn plugin and that allowed me to log in via direct webauthn authentication via my yubikey, while this plugin is still active. This might be an alternative route.

  15. 41 remaining items

  16. adampl commented on Oct 14, 2025

    @adampl

    is WebAuthn ever going to be implemented?

  17. modified the milestones: 0.14.2, 0.15.0 on Dec 11, 2025
  18. moved this from Backlog to In progress in Two Factor project boardon Feb 8, 2026
  19. moved this from In progress to In review in Two Factor project boardon Feb 8, 2026
  20. modified the milestones: 0.15.0, 0.16.0 on Feb 18, 2026
  21. masteradhoc commented on Feb 28, 2026

    @masteradhoc
    Collaborator

    Hey everyone
    We'll remove U2F support finally in 0.16.0. We'll track the Support of WebAuthn in #427 and a discussion to migrate U2F Keys to WebAuthn in #491 soon as well. Thanks everyone for your patience.

  22. removed this from the 0.16.0 milestone on Mar 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions