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
Allow Arbitrary OpenID providers in this bug tracker #52256
Comments
Currently the issue tracker only allows a handful of OpenID providers. The PYPI mailing list discussed the issue fo months, and finally PYPI opened to any OpenID provider. I would suggest to allow the same liberty, for the same reasons, here. |
Looking at the interface I assumed that any openid provider was supported. Did you try an alternate one and it didn't work? I'm using an id hosted on my own server (albeit delegating to myopenid). This bug actually belongs in the metatracker, by the way. (Which, unfortunately, doesn't support openid, but one thing at a time :) |
Trying to associate an "unsupported" OpenID provider is ignored. There is no "link" to login with an "unsuppported" OpenID provider. And yes, the report should be in the metatracker, but I don't have an account there, and they don't support OpenID at all (we do, so this "bug" belongs here :)) |
Well, 'we' and 'they' are pretty much the same team. If you want to enhance the openid support that Martin added to the tracker, you can submit a patch against the code in the repository. |
Closing as invalid -- how can we ask submitters to respect the rules if not even we committers do? |
Greog, please, elaborate. I want to learn :) |
I'm sorry, I was too short. I just meant that we should submit issues to the correct tracker :) |
Someway, the closed state vanished. |
Uhmmm... My browser seems crazy. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: