817886 - Refactor webpay to use solitude for JWT issuers/secrets

Status: RESOLVED FIXED

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

Description

[Kumar McMillan [:kumar]]

webpay should use the solitude API to validate and deal with JWT issuers/secrets. Currently webpay has a stub database table of issuers. This can be removed.

See: https://github.com/mozilla/solitude/blob/master/lib/sellers/models.py#L49
Also: https://github.com/mozilla/webpay/blob/master/webpay/pay/forms.py#L40

Comment 1

[Andy McKay]

The app_id is coming from the JWT, where's the matching field in solitude, is it external_id on SellerProduct?

Comment 2

[Kumar McMillan [:kumar]]

The app ID is whatever we want to make it. We will use this as a public identifier to lookup the seller's secret. I originally envisioned it as the seller uuid and I envisioned Marketplace setting seller uuid's to the domain name of the app. The product external ID is different; that is what gets passed through request.id in the JWT https://wiki.mozilla.org/WebAPI/WebPayment#In-app_payment

Comment 3

[Andy McKay]

I'll set it assume its going to be seller uuid for now, easy to change later.

Comment 4

[Andy McKay]

https://github.com/mozilla/webpay/commit/f33aee