Use the new AMO User API

RESOLVED FIXED in Q2 2012

Status

addons.mozilla.org Graveyard
Add-on Builder
P3
normal
RESOLVED FIXED
6 years ago
4 years ago

People

(Reporter: clouserw, Assigned: zalun)

Tracking

unspecified
Q2 2012

Details

(Reporter)

Description

6 years ago
Allen hooked up an endpoint for you to get user info out of AMO so you don't have to use the db.  An example URL (this is behind oauth - builder's user already has access):

> https://addons-dev.allizom.org/z/en-US/firefox/api/2/user/?email=clouserw@gmail.com

Which gives this output:

> {
>     "username": "clouserw",
>     "display_name": "clouserw",
>     "created": "2007-03-05 13:09:38",
>     "modified": "2012-01-31 12:38:50",
>     "id": 10482,
>     "location": "Portland, OR",
>     "homepage": "http://micropipes.com/blog/",
>     "email": "clouserw@gmail.com",
>     "occupation": "Internets"
> }

I chose those fields, it's easy to add/subtract if needed but I think that's all the builder uses.  Is there anything else we need?

Remember that bug last week where people couldn't log in to builder-dev?  Closing this bug will fix that. :)
(Assignee)

Updated

6 years ago
Target Milestone: --- → Builder 1.0
(Assignee)

Updated

6 years ago
Assignee: nobody → zaloon
Priority: -- → P3
(Assignee)

Updated

6 years ago
Target Milestone: Builder 1.0 → Q2 2012
(Assignee)

Comment 1

6 years ago
API is working fine with browserID/Persona
We've decided to remove old style authentication
(Assignee)

Updated

6 years ago
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Assignee)

Comment 2

6 years ago
Please provide what is returned if API can't find a user with given email.
I believe, before it was None
It seems to raise 404 right now.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Comment 3

6 years ago
it is 404 indeed
Status: REOPENED → RESOLVED
Last Resolved: 6 years ago6 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.