Skip to content

GitHub supports Web Authentication (WebAuthn) for security keys

The WebAuthn standard for security keys is making authentication as easy as possible. Now you can use security keys for second-factor authentication on GitHub with many more browsers and devices.

A security key registration prompt in Google Chrome, offering to "Verify your identity with" using either a USB security key or built-in biometric sensor.

GitHub now supports Web Authentication (WebAuthn) for security keys—the new standard for secure authentication on the web. Starting today, you can use security keys for two-factor authentication on GitHub with even more browsers and devices. And, since many browsers are actively working on WebAuthn features, we’re excited about the potential for strong and easy-to-use authentication options for the entire GitHub community in the future.

Register a new security key in your GitHub settings

More browsers, devices, and biometric options

Previously, GitHub supported physical security keys using the experimental U2F API for Chrome. WebAuthn is the standards-based successor. You can now use physical security keys on GitHub with:

  • Windows, macOS, Linux, and Android: Firefox and Chrome-based browsers
  • Windows: Edge
  • macOS: Safari, currently in Technology Preview but coming soon to everyone
  • iOS: Brave, using the new YubiKey 5Ci

But there’s more—GitHub’s move toward WebAuthn makes it possible to use your laptop or phone as a security key without carrying a separate physical key. If you’re using the following browsers, you can register your device today:

  • Microsoft Edge on Windows, using Windows Hello (with facial recognition, fingerprint reader, or PIN)
  • Chrome on macOS, using Touch ID
  • Chrome on Android, using fingerprint reader

And as new browsers and devices support WebAuthn, you’ll have even more choices for secure authentication that automatically work with GitHub.

Security key authentication prompts for GitHub in three browsers: Microsoft Edge on Windows using Windows Hello (fingerprint, PIN, or security key), Brave on iOS using the YubiKey 5Ci, and Chrome on Android using a fingerprint reader.

The future of authentication: secure and easy-to-use

Account security is critical for GitHub. Although we support strong authentication options, many people still don’t use a password manager or two-factor authentication because individual passwords have always been the easiest choice.

Because platform support is not yet ubiquitous, GitHub currently supports security keys as a supplemental second factor. But we’re evaluating security keys as a primary second factor as more platforms support them. In addition, WebAuthn can make it possible to support login using your device as a “single-factor” security key with biometric authentication instead of a password. Although we’re not ready to announce further plans, we’ll continue to pursue ways to make secure authentication as easy as possible for everyone on GitHub.

Implementing WebAuthn

Are you interested in supporting security keys as an authentication option for your web service? WebAuthn offers some of the strongest account protection around—and it’s easier than ever to implement in a variety of server programming languages using open source libraries available on GitHub. We’ve also open sourced @github/webauthn-json, a lightweight JavaScript wrapper around the WebAuthn API you might find useful. We’re excited to see how you’re making authentication more secure, easy, and flexible for your users.

Explore more from GitHub



Updates on GitHub products and features, hot off the press.
GitHub Universe 2024

GitHub Universe 2024

Get tickets to the 10th anniversary of our global developer event on AI, DevEx, and security.
GitHub Copilot

GitHub Copilot

Don't fly solo. Try 30 days for free.
Work at GitHub!

Work at GitHub!

Check out our current job openings.