-
Notifications
You must be signed in to change notification settings - Fork 987
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Require 2FA enrollment for all new users #13762
Comments
User Registration experience today:
At this point, there's nothing preventing the user from never verifying their email address, other than wanting to publish a package - Create API Token requires a verified email.
The question isAt what step of the flow should we require the user to enroll in 2FA?
Basically, something about the user registration flow has to change, and today we allow unverified registrations to continue to use the logged-in aspects of PyPI - manage collaborators, yank/delete releases, setup trusted publishing, etc. |
I think this makes sense. |
#14126 implemented the requirement for having a verified primary email for management actions other than account management. |
Hooks into security policy to require all non-account management actions to have a form of 2FA set up. Adds a time-based restriction for new users, which we can remove when we want to enforce for everyone. Resolves pypi#13762 Signed-off-by: Mike Fiedler <miketheman@gmail.com>
Thank you @miketheman ! |
Expand the policy to include file upload actions. Follows pypi#14294 Refs pypi#13762 Signed-off-by: Mike Fiedler <miketheman@gmail.com>
What's the problem this feature will solve?
Since we will require it for all uploads beginning in 2024, we should add 2FA enrollment for all new users as soon as possible.
Describe the solution you'd like
Add 2FA enrollment to routine new user registration flow.
The text was updated successfully, but these errors were encountered: