-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Support logging in with GitHub #7
Comments
Setup InstructionsGenerate a set of github oauth credentials here: Set the authorization callback url to be: Insert the client_id and client_secret into the database: INSERT INTO _oic_registration
(_issuer, _client_id, _client_secret, id)
VALUES ('https://github.com/settings/developers', 'xx', 'xx', x); PatchApplies to tracker/python-dev https://gist.github.com/ammaraskar/e259bc7d50df354e796e3c0d61137b10 |
@ezio-melotti Antoine said you'd be the right person to talk to about getting this merged. Lemme know if you want the patch in some specific way or another. |
A GitHub application managed by the python organization has been created with the name |
I still have not figured out how to register/login to bpo using GitHub account 😟 |
@berkerpeksag might also be able to answer, I think they mentioned this was disabled for some reason. |
It wasn't fully deployed for end users. By default, GitHub API doesn't include email addresses of users even if we set the OAuth scope correctly (users need to make their email address public on GitHub or we need to make a request to another endpoint in order to get their email address) I'm not going to work on it until I get a response from Barry regarding PEP 595. |
I've just re-pushed the patch with some modifications. I've already tested both Google and GitHub login supports locally. It should detect and associate existing bugs.python.org accounts with the same email address. The only limitation is that the email address must be set to public in user's email settings at GitHub. |
It would be great if we can login to bpo using GitHub.
Thanks.
The text was updated successfully, but these errors were encountered: