Closed
Bug 779278
Opened 12 years ago
Closed 12 years ago
Use the bluevia developer secret in the JWT
Categories
(Marketplace Graveyard :: Payments/Refunds, defect, P1)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: andy+bugzilla, Assigned: wraithan)
References
Details
Once the developer secret is populated, we need to alter the verify and create JWT resources to use the new developer secret... and change the unit tests to use that key correctly.
Even if the developer secret comes from the marketplace, we should never echo the developer secret back from remora, just the presence of the secret.
|
Reporter | |
Updated•12 years ago
|
Summary: Get the bluevia developer secret into solitude → Use the bluevia developer secret in the JWT
|
|
Reporter | |
Comment 1•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
|
|
Reporter | |
Comment 2•12 years ago
|
||
Comment 1 was on completely the wrong bug.
As per https://etherpad.mozilla.org/mkt-bluevia-devhub-flow, we have to traverse the secret back to the developer across the marketplace.
Assignee: nobody → xwraithanx
Status: RESOLVED → REOPENED
Priority: -- → P1
Resolution: FIXED → ---
|
Assignee | |
Updated•12 years ago
|
Target Milestone: --- → 2012-08-09
|
|
Assignee | |
Updated•12 years ago
|
Target Milestone: 2012-08-09 → 2012-08-16
|
||
Comment 3•12 years ago
|
||
We are currently discussing a different (better) way to sign JWTs. I'll update this bug when we have a decision.
Target Milestone: 2012-08-16 → ---
|
|
||
Comment 4•12 years ago
|
||
We aren't using BlueVia anymore but we still have dev secrets. You can see bug 797991 for info on that.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•