GitHub Mobile uses public-key cryptography to secure your account, allowing you to use any mobile device that you've used to sign in to GitHub Mobile as your second factor. In addition to security keys, you can also use GitHub Mobile for 2FA after configuring a TOTP mobile app or text messages. For more information, see ' WebAuthn' and ' Can I Use.' WebAuthn is the successor to U2F and works in all modern browsers. The technology that enables authentication with a security key is called WebAuthn. The only way someone can sign into your account is if they know both your password and have access to the authentication code on your phone.Īfter you configure 2FA, using a time-based one-time password (TOTP) mobile app, or via text message, you can add a security key, like a fingerprint reader or Windows Hello. After you enable 2FA, GitHub generates an authentication code any time someone attempts to sign into your account on. If you don't receive a notification, then you are not part of a group required to enable 2FA, though we strongly recommend it.įor more information about the 2FA enrollment rollout, see this blog post.įor GitHub, the second form of authentication is a code that's generated by an application on your mobile device or sent as a text message (SMS). If you are in an eligible group, you will receive a notification email when that group is selected for enrollment, marking the beginning of a 45-day 2FA enrollment period, and you will see banners asking you to enroll in 2FA on.

Note: Starting in March 2023 and through the end of 2023, GitHub will gradually begin to require all users who contribute code on to enable one or more forms of two-factor authentication (2FA).

1password 2 factor authentication