16.50 KB, text/plain
5.43 KB, text/plain
Juicy details are here: http://forums.mozillazine.org/viewtopic.php?f=38&t=1778945&p=8843565
I can reproduce this, however it looks to be a server issue. See attached API dialog comparison for details.
Dave, Can you hone in for us on the particular data that points to it being a server issue.
The first authentication call (before changing my email) works as expected - a valid authentication token is returned and I can download my list of collections. The second authentication call (after changing my email) does not work - a authentication token is returned, but further API calls with that token are rejected with an "unauthorized" error. Since nothing has changed on the client side (we only store tokens locally, not usernames or email) then the assumption is that the server API does not handle email changes correctly - perhaps some table is incorrectly indexed on email not id.
Les, Are you still working on Collections these days. Is this something you can look into?
Assignee: dave → nobody
Component: Collector Extension → Collections
QA Contact: collector-extension → collections
Assignee: nobody → lorchard
Target Milestone: BW-1.1.2 → ---
Version: BW-1.1.x → unspecified
No, I haven't worked on AMO in a year or so
Assignee: lorchard → nobody
Dave is working on the API these days.
Assignee: nobody → dd
Priority: P1 → P3
Target Milestone: --- → 4.x (triaged)
Assignee: dd → nobody
Collector 2.1 is shipping in a matter of days and it will be the last version in its current form. The API will not longer be maintained --> WONTFIX
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WONTFIX
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.