Universal 2nd Factor (U2F)

From wikieduonline
Revision as of 12:08, 15 February 2024 by Welcome (talk | contribs) (→‎Related terms)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

wikipedia:Universal 2nd Factor (2014) uses NFC or USB.


Support and use

U2F security keys are supported by Google Chrome since version 38[1] and Opera since version 40. U2F security keys can be used as an additional method of two-step verification on online services that support the U2F protocol, including Google,[1] Dropbox,[2] GitHub,[3] GitLab,[4] Bitbucket,[5] Nextcloud,[6] Facebook,[7] and others.[8]

Chrome, Firefox, and Opera were, Template:As of, the only browsers supporting U2F natively. Microsoft has enabled FIDO 2.0 support for Windows 10's Windows Hello login platform.[9] Microsoft Edge[10] browser gained support for U2F in the October 2018 Windows Update. Microsoft accounts, including Office 365, OneDrive, and other Microsoft services, do not yet have U2F support. Mozilla has integrated it into Firefox 57, and enabled it by default in Firefox 60[11][12][13][14] and Thunderbird 60.[15] Microsoft Edge starting from build 17723 support FIDO2.[16]. As of iOS and iPadOS 13.3 Apple now supports U2F in the Safari browser on those platforms.


AWS CLI v2 doesn’t yet support Universal 2nd factor (U2F) MFA. As a workaround, you can use YubiKey as a virtual device MFA. [17]

Related terms

See also

Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Source: wikipedia

  1. 1.0 1.1 Cite error: Invalid <ref> tag; no text was provided for refs named Using Security Key
  2. Cite error: Invalid <ref> tag; no text was provided for refs named Auto58-1
  3. Cite error: Invalid <ref> tag; no text was provided for refs named Auto58-2
  4. Cite error: Invalid <ref> tag; no text was provided for refs named Auto58-3
  5. Cite error: Invalid <ref> tag; no text was provided for refs named Auto58-4
  6. Cite error: Invalid <ref> tag; no text was provided for refs named Auto58-5
  7. Cite error: Invalid <ref> tag; no text was provided for refs named Auto58-6
  8. Cite error: Invalid <ref> tag; no text was provided for refs named Auto58-7
  9. Cite error: Invalid <ref> tag; no text was provided for refs named Auto58-8
  10. Cite error: Invalid <ref> tag; no text was provided for refs named Auto58-9
  11. Cite error: Invalid <ref> tag; no text was provided for refs named Auto58-10
  12. Cite error: Invalid <ref> tag; no text was provided for refs named Auto58-11
  13. Cite error: Invalid <ref> tag; no text was provided for refs named Auto58-12
  14. Cite error: Invalid <ref> tag; no text was provided for refs named Auto58-13
  15. Cite error: Invalid <ref> tag; no text was provided for refs named Auto58-14
  16. Cite error: Invalid <ref> tag; no text was provided for refs named Auto58-15
  17. https://aws.amazon.com/blogs/security/enhance-programmatic-access-for-iam-users-using-yubikey-for-multi-factor-authentication/

Advertising: