Closed Bug 984526 Opened 11 years ago Closed 11 years ago

Cope correctly with incoming in-app payments in webpay

Categories

(Marketplace Graveyard :: Payments/Refunds, defect, P2)

Product:
Marketplace Graveyard
Component:
Payments/Refunds
Version:
Avenir
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED
Milestone:
2014-05-27

People

(Reporter: andy+bugzilla, Assigned: jlockhart)

References

Details

(Whiteboard: [qa-])

We decided that the best way to sign JWTs for the easier in-app payments is to use the marketplace key and secret. That means that the issuer for apps and in-app payments is now the same. Previously webpay used the issuer to distinguish between the two and then do the extra work that an in-app payment needed. We'll need to alter webpay to check more data in the JWT. I'm guessing the check needs to be done here: https://github.com/mozilla/webpay/blob/master/webpay/pay/tasks.py#L151-L152 How an in-app gets identified in the JWT Jared is adding.
Priority: -- → P2
Assignee: nobody → jkerim
Target Milestone: --- → 2014-05-27
This might fall into place after bug 1016685
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.