Closed
Bug 1070155
Opened 10 years ago
Closed 10 years ago
Define and document the API for add-on signing
Categories
(addons.mozilla.org Graveyard :: Code Quality, defect, P1)
addons.mozilla.org Graveyard
Code Quality
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: clouserw, Assigned: rtilder)
References
Details
To sign add-ons according to the plan[1] we need to pass in at least the add-on ID to Trunion so it can put that into the cert as part of the Common Name.
After the signing is done, AMO needs to know the certificate serial number. We could pull this out of the returned add-on, or if Trunion is returning a blob to us anyway, we could put it in there.
In short, we need to document what the ins and outs should look like. :)
[1] https://docs.google.com/a/mozilla.com/document/d/1KhpDteoHFmVRkzlrT8v0N3F-KrPxLoZFM3mWmEmOses/edit
Assignee | ||
Comment 2•10 years ago
|
||
API defined here: https://wiki.mozilla.org/AMO/SigningService/API
Reporter | ||
Comment 3•10 years ago
|
||
is there more to do on this bug?
Assignee | ||
Comment 4•10 years ago
|
||
Nope. Should have been closed months ago.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•