Closed
Bug 912027
Opened 11 years ago
Closed 11 years ago
Support token check API for verifying Bango responses
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
2013-09-17
People
(Reporter: andy+bugzilla, Assigned: kumar)
Details
(Whiteboard: [qa-])
The relay API was added in bug 887345, we need to implement and use the relay API so that we confirm incoming requests from Bango against Bango.
|
Reporter | |
Comment 1•11 years ago
|
||
Some great comments in this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=887345#c16
|
|
Reporter | |
Updated•11 years ago
|
Assignee: nobody → kumar.mcmillan
|
Assignee | |
Updated•11 years ago
|
Priority: -- → P1
|
|
Assignee | |
Comment 2•11 years ago
|
||
I can't get the token check service to work, details in bug 914263
Depends on: 914263
|
|
Assignee | |
Updated•11 years ago
|
Summary: Support relay API → Support token check API for verifying Bango responses
|
|
Assignee | |
Comment 3•11 years ago
|
||
WIP patch: https://github.com/kumar303/solitude/compare/master...token
|
|
Assignee | |
Comment 4•11 years ago
|
||
Support for checking tokens has landed but it's disabled in prod until bug 914263 is fixed. Solitude: https://github.com/mozilla/solitude/commit/bae1c0453c9f9639b41ee08eee182e60396c4df2 Webpay: https://github.com/mozilla/webpay/commit/11296803a5f6170cd1ac7f56e40f17c17ea13df6
|
|
Assignee | |
Comment 5•11 years ago
|
||
Since this is done I'm going to close it. We're waiting on Bango for some fixes though -- see bug 915359 for enabling token checks.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2013-09-17
|
||
Comment 6•11 years ago
|
||
Can you please add some STRs to this bug or mark it as [qa-] ?
|
|
Assignee | |
Comment 7•11 years ago
|
||
The STR would be quite complicated since it involves building a custom B2G with a proxy in front of Bango's payment URL. I'll just qa- for now. We're relying on peer review to qa this logic.
Whiteboard: [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•