Closed Bug 724648 Opened 12 years ago Closed 12 years ago

Use the new AMO User API

Categories

(addons.mozilla.org Graveyard :: Add-on Builder, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED
Q2 2012

People

(Reporter: clouserw, Assigned: zalun)

Details

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. :)
Target Milestone: --- → Builder 1.0
Assignee: nobody → zaloon
Priority: -- → P3
Target Milestone: Builder 1.0 → Q2 2012
API is working fine with browserID/Persona
We've decided to remove old style authentication
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
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 → ---
it is 404 indeed
Status: REOPENED → RESOLVED
Closed: 12 years ago12 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.