The UI for enabling the secure 2FA requirement is inaccurate

[mbainter]

Select Topic Area

Product Feedback

Body

When migrating an organization into an Enterprise that requires 2FA and only Secure 2FA methods it pops up an information window to make sure you understand how it will affect the users of that organization, including a count of the number of users who will be affected by the new requirement.

In theory, this is supposed to tell you about who will be affected by the change in policy. The problem is, the way the feature is implemented, you not only need to have Secure 2FA enabled, you are not allowed to have any insecure 2FA methods enabled, regardless of whether or not you use it to authenticate. This is reasonable, as otherwise someone who is able to hijack an SMS code for example could then simply change the other methods to something they control. Making this feature useful requires that.

The problem is, whatever query is being used in that popup window only seems to query how many users in the organization do not have a Secure 2FA method enabled, when it should be querying both how many don't don't have one enabled, AND how many have it enabled but also have an insecure method enabled. Ideally it would show those as two different counts, but at a minimum the total count should cover both possibilities.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐