This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Login to bugs.python.org with Google account NOT working
Type: Stage: resolved
Components: Versions:
process
Status: closed Resolution: third party
Dependencies: Superseder:
Assigned To: Nosy List: ruffsl, terry.reedy
Priority: normal Keywords:

Created on 2018-02-19 21:41 by ruffsl, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (2)
msg312374 - (view) Author: (ruffsl) * Date: 2018-02-19 21:41
I've been unable to login to bugs.python.org using Google's oauth.

After clicking the google oauth logo on the sidebar on bugs.python.org, I am either slowly redirected to a google login page (after about 1 min) to select an account, then after selecting the relevant google account or if I'm only active in it, I'm eventually given a error message after about 2 min of loading time:

``` html
<html><head><title>An error has occurred</title></head>
<body><h1>An error has occurred</h1>
<p>A problem was encountered processing your request.
The tracker maintainers have been notified of the problem.</p>
</body></html>
```

Other outputs from the browser debug console:
```
Failed to load resource: the server responded with a status of 404 (/tracker/favicon.ico)
Failed to load resource: the server responded with a status of 500 (Internal Server Error)
```
This has persisted for about a week now, on multiple machines, bowsers, and ISPs. Presently, the only way I've been able to post this issue at all is due to my first and only login session on one workstation is still active. I suspect this might be a larger issue, only that no one else using google oauth to login has been able to login to file and voise the bug?

Related?
https://bugs.python.org/issue29544
https://bugs.python.org/issue28887
msg312676 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2018-02-24 00:22
This is similar to #29544.  As the reply there indicates, this tracker (for issues with the cpython repository) is the wrong place for issues about the tracker.  Click Report Tracker Problem on the left sidebar.
History
Date User Action Args
2022-04-11 14:58:58adminsetgithub: 77058
2018-02-24 00:22:20terry.reedysetstatus: open -> closed

nosy: + terry.reedy
messages: + msg312676

resolution: third party
stage: resolved
2018-02-19 21:41:08ruffslcreate