-
Notifications
You must be signed in to change notification settings - Fork 995
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
Make QR code for TOTP more specific, informative #5894
Comments
@di @woodruffw If this is easy, let's try to get it in before we wrap up the OTF milestone? |
Just confirming over here too that #5809 is the same thing I was after with my request. Thanks all! |
Hmm, so this is how we're generating the TOTP provisioning URI: otp.generate_totp_provisioning_uri(
totp_secret,
self.request.user.username,
issuer_name=self.request.registry.settings["site.name"],
) Which yields a URI like this:
So, TOTP applications should have enough information to unambiguously identify (Warehouse, username) tuples. For example, this is what I get with Google Authenticator: Whereas for Duo: Fixing this is a bit of a double-edged sword: we could change the Edit: For reference: https://github.com/google/google-authenticator/wiki/Key-Uri-Format |
Somewhat related: we can change the issuer name from |
@steiza do I recall correctly that there's an update on the Duo Mobile side that partially addresses this issue? |
Oops! Sorry, I'm not sure how I missed this back in May. I haven't worked on the mobile app, but my understanding is that if the URI contains
If the issuer is set to any other value, like This isn't ideal, but it shouldn't be confusing to users of pypi.org. I can definitely see how this would be confusing to users of test.pypi.org. |
What's the problem this feature will solve?
The QR code (for Duo Mobile, at least) produces an entry with just the username, which is ambiguous to the user.
Describe the solution you'd like
More helpful would be, e.g.,
test.pypi.org-$username
to show which PyPI (and really which site) the account is for, AND which account it is.Additional context
Submitted at the PyCon North America sprints by signop who is probably @signop; thank you for testing!
cc @steiza
The text was updated successfully, but these errors were encountered: