Unable to link profile to People due to error page not being rendered properly
Categories
(bugzilla.mozilla.org :: General, defect)
Tracking
()
People
(Reporter: aaronmt, Unassigned)
Details
Attachments
(1 file)
On attempt to link my (this) account to People, I recieve
An internal error has occurred, but Bugzilla doesn't know what Bugzilla::CGI->header() should only be called from inside Bugzilla::App::CGI! at /app/Bugzilla/CGI.pm line 430 means. If you are a Bugzilla end-user seeing this message, please save this page and send it to bmo-mods@mozilla.com.
STR:
On the Request for access to your account
page, click Allow
, see error above.
Comment 1•3 years ago
|
||
I have seen this reported a couple times but have not been able to reproduce it. Are you clicking 'Allow' on the screen asking if you want to create a new account where one does not yet exist?
Comment 2•3 years ago
|
||
Also how are you logging into Bugzilla when trying to link the account with people.mozilla.org? Are you using a Github account or creating an username and password directly in Bugzilla?
Reporter | ||
Comment 3•3 years ago
•
|
||
I have seen this reported a couple times but have not been able to reproduce it. Are you clicking 'Allow' on the screen asking if you want to create a new account where one does not yet exist?
I'm clicking Allow
on the Request for access to your account
. One detail I missed that seems to be reproducible is that the fist click on Allow
essentially hangs in load. Clicking Allow
again immediately forwards me to the Bugzilla::CGI->header()
error.
Also how are you logging into Bugzilla when trying to link the account with people.mozilla.org? Are you using a Github account or creating an username and password directly in Bugzilla?
I'm still using the old style login u/p w/2FA on Bugzilla (not via Github).
I've attempted to logout, and re-login on BMO and People and it made no difference.
Updated•3 years ago
|
Comment 4•3 years ago
|
||
Comment 5•3 years ago
|
||
This fix is live in production now. Can you try your action again and see if it fixes it or gives us some other indication of what may be wrong? Thanks
Reporter | ||
Comment 6•3 years ago
•
|
||
Upon clicking Allow
for Request for access to your account
, the request seems to hang. No difference on follow-up attempts clicking Allow
.
On clicking Allow
in console I see 2 errors
Failed to load resource: the server responded with a status of 404 ()
on https://bugzilla.mozilla.org/static/v20220810.1/js/lib/md5.min.js.map
and
Refused to load https://people.mozilla.org/whoami/bugzilla/auth?code=eyJhbGciOiJIUzI1NiJ9.eyJqdGkiOiJVcnZhNjA5SXdOOU5pMXNoOXRUWmR6c0trM1pPSExXMyIsInVzZXJfaWQiOjI5OTk0MiwiYXVkIjoiaHR0cHM6Ly9wZW9wbGUubW96aWxsYS5vcmcvd2hvYW1pL2J1Z3ppbGxhL2F1dGgiLCJzY29wZXMiOlsidXNlcjpyZWFkIl0sInR5cGUiOiJhdXRoIiwiY2xpZW50IjoiTHJGaTdidUo5OXd2SHllRDFXa0ciLCJpYXQiOjE2NjAyNDkzMDgsImV4cCI6MTY2MDI0OTkwOH0.NlkW4_L3J0qdXZMjrPqIhoZg4a59xixnHJyxvi3h2wI&state=1LjQyC6xn-Iobb6rDKamRA because it does not appear in the form-action directive of the Content Security Policy.
with a different code on each click
Comment 7•3 years ago
|
||
Ok thanks for the information. That is definitely something more to go on. Will see if I can investigate more now.
Comment 8•3 years ago
|
||
(In reply to David Lawrence [:dkl] from comment #7)
Ok thanks for the information. That is definitely something more to go on. Will see if I can investigate more now.
Still looking at this. It works fine for me and in most cases. It is a corner case that I am still trying to nail down. This happens every time right?
Reporter | ||
Comment 9•3 years ago
|
||
I tried again. On attempt to click Allow today nothing happens. On inspect and in web-console on each attempt to click Allow I see logged
Refused to send form data to 'https://bugzilla.mozilla.org/oauth/authorize?oauth_confirm_LrFi7buJ99wvHyeD1WkG=1&token=1674500638-1GQNWysjVCfx9OzYFoMIk3e_l2NAGZIQllx9EArPO48&submit=Allow&client_id=LrFi7buJ99wvHyeD1WkG&redirect_uri=https%3A%2F%2Fpeople.mozilla.org%2Fwhoami%2Fbugzilla%2Fauth&response_type=code&scope=user%3Aread&state=G1guMSfnOK92iOqjAq1P0g' because it violates the following Content Security Policy directive: "form-action 'self' https://www.google.com/search https://phabricator.services.mozilla.com/".```
Comment 10•3 years ago
|
||
Comment 11•3 years ago
|
||
Merged. Let's give this a try. Will try to get this live today.
https://github.com/mozilla-bteam/bmo/commit/937555d3ad953dd3a96c5033b10e133e2ae16133
Comment 12•3 years ago
|
||
(In reply to Aaron Train [:aaronmt] from comment #9)
I tried again. On attempt to click Allow today nothing happens. On inspect and in web-console on each attempt to click Allow I see logged
Refused to send form data to 'https://bugzilla.mozilla.org/oauth/authorize?oauth_confirm_LrFi7buJ99wvHyeD1WkG=1&token=1674500638-1GQNWysjVCfx9OzYFoMIk3e_l2NAGZIQllx9EArPO48&submit=Allow&client_id=LrFi7buJ99wvHyeD1WkG&redirect_uri=https%3A%2F%2Fpeople.mozilla.org%2Fwhoami%2Fbugzilla%2Fauth&response_type=code&scope=user%3Aread&state=G1guMSfnOK92iOqjAq1P0g' because it violates the following Content Security Policy directive: "form-action 'self' https://www.google.com/search https://phabricator.services.mozilla.com/".```
A change has been pushed live to address this error. Can you try to do the linking again and let me know if anything changes?
Thanks
Reporter | ||
Comment 13•3 years ago
|
||
That seemed to do the trick. I'm able to follow through verification now.
Comment 14•3 years ago
|
||
Awesome. We can leave this closed then I think until someone else has an issue.
Description
•