On GitHub, type the code into the field under "Verify the code sent to your phone" and click Continue. You'll receive a text message with a security code. When your information is correct, click Send authentication code. Under "Setup SMS authentication", select your country code and type your mobile phone number, including the area code. For more information, see " Countries where SMS authentication is supported".Īt the bottom of the page, next to "SMS authentication", click Select.Ĭomplete the CAPTCHA challenge, which helps protect against spam and abuse. Before configuring authentication via text message, review the list of countries where GitHub supports authentication via SMS. GitHub doesn't support sending SMS messages to phones in every country. Warning: We strongly recommend using a TOTP application for two-factor authentication instead of SMS, and security keys as backup methods instead of SMS. If you're unable to configure a TOTP mobile app, you can also register your phone number to receive SMS messages.īefore using this method, be sure that you can receive text messages. For more details on how to configure each additional method, see " Configuring two-factor authentication" and " Configuring two-factor authentication".Ĭonfiguring two-factor authentication using text messages Optionally, you can configure additional 2FA methods to reduce your risk of account lockout. Save them to a secure location because your recovery codes can help you get back into your account if you lose access.Īfter saving your two-factor recovery codes, click I have saved my recovery codes to enable two-factor authentication for your account. Under "Save your recovery codes", click Download to download your recovery codes to your device. On GitHub, type the code into the field under "Verify the code from the app". The TOTP mobile application saves your account on and generates a new authentication code every few seconds. If you can't scan the QR code, click enter this text code to see a code that you can manually enter in your TOTP app instead.After scanning, the app displays a six-digit code that you can enter on GitHub. Scan the QR code with your mobile device's app.Under "Setup authenticator app", do one of the following: In the "Two-factor authentication" section of the page, click Enable two-factor authentication. In the "Access" section of the sidebar, click Password and authentication. In the upper-right corner of any page, click your profile photo, then click Settings. If 2FA is already enabled and you want to add another device, you must re-configure your TOTP app from your security settings. Tip: To configure authentication via TOTP on multiple devices, during setup, scan the QR code using each device at the same time. For users other than the setup user, an administrator must configure 2FA on your identity provider (IdP). If you're a member of an enterprise with managed users, you cannot configure 2FA for your managed user account account unless you're signed in as the setup user. If you cannot perform 2FA to pass the checkup, you must use the provided shortcut to reconfigure your 2FA settings and retain access to. Otherwise, you will be prompted to perform 2FA in an existing session on the 28th day. You can leave the check up period by successfully performing 2FA in those 28 days. Many TOTP apps support the secure backup of your authentication codes in the cloud and can be restored if you lose access to your device.Īfter you configure 2FA, your account will enter a 28-day check up period. TOTP applications are more reliable than SMS, especially for locations outside the United States. We strongly recommend using a time-based one-time password (TOTP) application to configure 2FA, and security keys as backup methods instead of SMS. You can configure two-factor authentication (2FA) using a mobile app or via text message. 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. 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).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |