Replies: 5 comments 3 replies
-
Hi @TSlam1993 👋 Thanks for reaching out. Can you let us know in which context you are referring to the QR code scanning? If you are referring to the 2FA, then the GitHub Mobile apps are not authenticator apps and we are not offering authenticator capabilities. For that case you need to configure TOTP first with an authenticator app, such as Microsoft Authenticator to be able to use 2FA with GitHub Mobile as mentioned in our docs 🙇
This is quite interesting. Are you using our Android or the iOS app? Thanks in advance! |
Beta Was this translation helpful? Give feedback.
-
which context are u referring or searching for, are u searching for an authentication QR code on a website or something like this? |
Beta Was this translation helpful? Give feedback.
-
Hello!
I am using an Android Phone (Galaxy S21 Ultra), One UI version 6.1, Android
version 14, last updated 1 september 2024.
I open Github on desktop and it asks me to create 2FA.
[image: image.png]
[image: image.png]
I see now that it says to use "authenticator app" and doesn't refer to
GithubMobile as one, but I was under the impression it would be, because it
says in the email:
[image: image.png]
ср, 27 нояб. 2024 г. в 15:28, SAIF003 ***@***.***>:
… which context are u referring or searching for, are u searching for an
authentication QR code on a website or something like this?
—
Reply to this email directly, view it on GitHub
<#145625 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AMWL4PGEUINYGY6PGNR45XD2CWUHVAVCNFSM6AAAAABSP4BWBGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZZGMYTQNY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Here's the email I received from Github about 2FA, which led me to believe
that 2FA can be done via mobile (and assume via QR Scan) - can you clarify
if there is a way to do that with GithubMobile?
…---------- Forwarded message ---------
От: GitHub ***@***.***>
Date: ср, 13 нояб. 2024 г. в 06:34
Subject: [ACTION REQUIRED] Your GitHub account, TSlam1993, will soon
require 2FA
To: TSlam1993 ***@***.***>
Hey TSlam1993!
This is a reminder that we announced
<https://github.blog/2022-05-04-software-security-starts-with-the-developer-securing-developer-accounts-with-2fa/>
that we are requiring users contributing code on GitHub.com to enable
two-factor authentication (2FA). You are receiving this notification
because your account meets this criteria and will be required to enroll in
2FA by November 14th, 2024 at 00:00 (UTC).
Please see the below FAQ, or learn more about 2FA on GitHub Help.
<https://docs.github.com/authentication/securing-your-account-with-two-factor-authentication-2fa/about-two-factor-authentication>
What you need to know about the required 2FA initiative
We are enrolling GitHub users who manage or author code on GitHub. More
information about our efforts to make 2FA adoption easy and safe can be
found in this blog post.
<https://github.blog/2023-03-09-raising-the-bar-for-software-security-github-2fa-begins-march-13>
This is a GitHub.com program, and unrelated to any organization or
enterprise membership your account may have.
How will this affect my account?
On November 14th, 2024 at 00:00 (UTC) your account will be required to have
2FA for authentication. If you have not yet enrolled by that date, your
ability to access GitHub.com will be limited until you finish the
enrollment process.
How do I enroll in 2FA?
Click here to get started!
<https://github.com/settings/two_factor_authentication/setup/intro> Prior
to November 14th, 2024 at 00:00 (UTC) you can follow the instructions in
our documentation
<https://docs.github.com/articles/configuring-two-factor-authentication> to
set up 2FA for your account. If you have not yet enrolled in 2FA by
November 14th, 2024 at 00:00 (UTC), you will automatically be taken to the
2FA enrollment form the next time you access GitHub.com.
What forms of 2FA can I use?
We want you to have the most seamless experience with 2FA possible, so you
can choose one or more of the following options:
- Security key
- GitHub Mobile
- Authenticator application (TOTP)
- Text messages (SMS)
You should set up at least two of these options, to ensure you always have
access to your account. Head to https://github.com/settings/security to
enroll more 2FA methods.
I already have 2FA enabled, do I need to do anything?
No, if you already have 2FA enabled before November 14th, 2024 at 00:00
(UTC), you don't need to take any additional actions. After November 14th,
2024 at 00:00 (UTC), you will no longer be able to unenroll from 2FA from
your account, but you will be able to change the option you use for
authenticating with 2FA. Additionally, you won't see any more banners on
GitHub.com, and we won't email you about this anymore.
What happens to my PATs and SSH keys at the deadline?
Your PATs, SSH keys, and applications will all keep working after the
deadline, regardless of your 2FA enrollment. PATs in particular are used
extensively in important automation, and interruption there can cause
outages in critical systems. However, when it is time to sign in to
GitHub.com to create a new PAT or manage your account, you'll be required
to enable 2FA before you can proceed.
What do I do if I lose my 2FA device?
GitHub strongly encourages the use of multiple second factor options. If
you lose all of your second factors, recovery codes are the only way to
access your account again. By saving your recovery codes, you'll be able to
regain access.
Be sure to enable cloud backup for your authenticator app and save your
recovery codes. Many phones and computers can be security keys as well -
registering them with GitHub.com gives you additional, highly-secure 2FA
methods.
For security reasons, GitHub Support may not be able to restore access to
accounts with 2FA enabled if you lose your 2FA credentials and lose access
to your account recovery methods.
More information about recovery codes can be found on GitHub Help at
https://docs.github.com/articles/recovering-your-account-if-you-lose-your-2fa-credentials
Why is GitHub requiring 2FA?
Ensuring account security is a shared responsibility GitHub takes
seriously. Strong authentication and the use of 2FA have been recognized as
best practice for many years. We feel that GitHub has a duty to lead this
push toward strong authentication as part of protecting the software supply
chain.
To see this and other security events for your account, visit your account
security audit log. <https://github.com/settings/security-log>
If you run into problems, please contact support by visiting the GitHub
support page. <https://github.com/contact>
Thanks,
The GitHub Team
|
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
the question is jn the title
and your search for similar discussions also doesn't work as typing "qr code" there and pressing enter doesnt do anything
Beta Was this translation helpful? Give feedback.
All reactions