Closed
Bug 905984
Opened 13 years ago
Closed 13 years ago
Internal server error on login into marketplace
Categories
(Marketplace Graveyard :: API, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
2013-09-03
People
(Reporter: orvils, Assigned: ashort)
Details
(Whiteboard: [qa+])
When trying to log into Mozilla marketplace with my persona account orvils@gmail.com I get error 500
"NetworkError: 500 INTERNAL SERVER ERROR - https://marketplace.firefox.com/users/browserid-login"
There was exactly the same error for my account a few months ago but I can't find that bug right now
Comment 1•13 years ago
|
||
Where are you seeing that error? Can you provide steps to reproduce?
Flags: needinfo?(orvils)
| Reporter | ||
Comment 2•13 years ago
|
||
Error is visible in the Firebug console when I try to log into with my persona account.
Today got additional error messages
"NetworkError: 500 INTERNAL SERVER ERROR - https://marketplace.firefox.com/api/v1/account/login/?lang=en-US&pro=8a7dd4dc.32.1®ion=worldwide"
[req] Request failed: POST 500
[req] Error message: 'NoneType' object has no attribute 'backend'
[login] Assertion verification failed! INTERNAL SERVER ERROR 500
Steps for the bug:
1. Click Sign in on https://marketplace.firefox.com/
2. Choose my persona orvils@gmail.com and wait for the login to complete
3. Error "Persona login failed. A server error was encountered." appears after the persona window closes and i see the errors above in the developer console
Flags: needinfo?(orvils)
Comment 3•13 years ago
|
||
Sounds like an API error. There should be a sentry traceback associated with this, I'd imagine.
Component: General → API
Updated•13 years ago
|
Assignee: nobody → ashort
Priority: -- → P1
| Assignee | ||
Comment 4•13 years ago
|
||
Looking at this account in the database, I'm seeing a different email address in `users` for this account ID from the gmail address mentioned here, which shows up in `auth_user`.
| Assignee | ||
Comment 5•13 years ago
|
||
So here's what's happening:
Changing your email address on AMO changes `users` only, not `auth_user`.
so if you have an AMO account created with `alice@example.com`, and then later change it to `bob@example.com`, then users will have the new address and auth_user will have the old one.
When login via Persona is done, the lookup is done in the users table. So if I try to log into Marketplace with `alice@example.com`, no account will be found. The Persona login process then creates a new users entry, and then attempts to create an auth_user entry. But since our auth_user table has a unique constraint on email address, this will fail. Subsequent logins will fail because the users entry exists with no corresponding auth_user entry.
The solution I propose, short term, is to hunt for auth_user entries by email address when encountering this situation and point the user entry at them. I don't foresee any security issues here because persona login disregards passwords, the only other personal information on the auth_user entry.
Long term, of course, we should upgrade to Django 1.5 and jettison auth_user entirely.
Comment 6•13 years ago
|
||
(In reply to Allen Short [:ashort] from comment #4)
> Looking at this account in the database, I'm seeing a different email
> address in `users` for this account ID from the gmail address mentioned
> here, which shows up in `auth_user`.
bug 878867 (I know you're already cc'd on that one Allen, but for other people)
Comment 7•13 years ago
|
||
Thanks for the investigation. Hooking them up manually sounds good to me. Any idea on how many there are? If you cook up some SQL or python I can help spot check.
| Assignee | ||
Comment 8•13 years ago
|
||
Working on a patch now to do this at login time so the problem won't recur.
Comment 9•13 years ago
|
||
(In reply to Wil Clouser [:clouserw] from comment #7)
> Thanks for the investigation. Hooking them up manually sounds good to me.
> Any idea on how many there are? If you cook up some SQL or python I can
> help spot check.
using the sql in https://bugzilla.mozilla.org/show_bug.cgi?id=878867#c0 - 9238 now
| Assignee | ||
Comment 10•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2013-09-03
Updated•13 years ago
|
Whiteboard: [qa+]
| Reporter | ||
Comment 12•13 years ago
|
||
I still have this error.
Is there some time until the patch goes to production?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
| Assignee | ||
Comment 13•13 years ago
|
||
Yes. Give it a try on https://marketplace-dev.allizom.org/ in the meantime.
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•