Closed
Bug 757987
Opened 12 years ago
Closed 12 years ago
bigtent: update idproxy config
Categories
(Cloud Services :: Operations: Miscellaneous, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: petef, Assigned: gene)
References
Details
(Whiteboard: [qa+])
update idproxy config with list of URLs that bigtent servers will need to use to talk to third-party services for authentication callbacks/etc.
Updated•12 years ago
|
Whiteboard: [qa?]
Reporter | ||
Updated•12 years ago
|
Group: services-infra
Comment 1•12 years ago
|
||
Per https://github.com/mozilla/browserid-bigtent/issues/23 Here are the URLs by service... If a url has a template below it, it has pieces that vary per user. For gmail.com: GET https://www.google.com/accounts/o8/id POST https://www.google.com/accounts/o8/ud GET https://www.google.com/accounts/o8/id?id=AItOawnGECMktY2XvE8OVvDYev69a3BuCIPt00E template - https://www.google.com/accounts/o8/id?id={token} For yahoo.com: GET http://open.login.yahooapis.com/openid20/www.yahoo.com/xrds POST https://open.login.yahooapis.com/openid/op/auth GET https://me.yahoo.com/a/wS1JKacQi4p4xQo18GMr_WME7g-- template: https://me.yahoo.com/{token} GET https://open.login.yahooapis.com/openid20/user_profile/xrds For hotmail.com: POST https://oauth.live.com/token GET https://apis.live.net/v5.0/me?access_token=EwAgAq1DBAAUl...reallylong...tmwdrX30YoAAA%3D%3D template: https://apis.live.net/v5.0/me?access_token={token}
Updated•12 years ago
|
Whiteboard: [qa?] → [qa+]
Reporter | ||
Comment 2•12 years ago
|
||
configs updated in stage. once verified, we'll schedule a production deploy.
Assignee: nobody → petef
Status: NEW → ASSIGNED
Updated•12 years ago
|
Assignee: petef → gene
Assignee | ||
Comment 3•12 years ago
|
||
Let me know when these configs are confirmed and we can deploy to prod. I'll wait to hear in this ticket.
Comment 4•12 years ago
|
||
We can verify this once the yahoo flow is working end to end.
Assignee | ||
Comment 5•12 years ago
|
||
The staging proxy logic was promoted to production and deployed 11/27/2012 in sysadmins r53318
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•