Please modify the schema for the intermediates collection to include more valuable metadata
Categories
(Cloud Services :: Server: Remote Settings, enhancement)
Tracking
(Not tracked)
People
(Reporter: jcj, Assigned: leplatrem)
References
(Blocks 2 open bugs)
Details
Attachments
(1 file)
(deleted),
text/x-github-pull-request
|
Details |
We'd like to add a new pair of properties to the schema for intermediate records to simplify the CRLite implementation in Firefox:
"subjectDN": {
"type": "string",
"title": "Binary Subject DN",
"description": "The certificate's subject distinguished name, in binary, as a base64-urlencoded string"
}
"derHash": {
"type": "string",
"title": "sha256 hash of the DER certificate attachment",
"description": "Binary sha256 hash of the DER bytes of the certificate, as a base64-urlencoded string"
}
This should be applied to the schema for: https://settings.stage.mozaws.net/v1/buckets/security-state/collections/intermediates/records (and the production equivalent on verification of the change).
Thanks!
Assignee | ||
Comment 1•5 years ago
|
||
Sure!
If you are interested, or want to accelerate, you can also do the changes yourself: you can modify the schema here in YAML:
https://github.com/mozilla-services/remote-settings-permissions/blob/85919a41c110b924d5bdb6883783343f6da26794/kinto.prod.yaml#L1463-L1506
When the PR is merged, it's deployed immediately in stage and prod.
I don't see a schema change as a risky operation, nonetheless if you really want to test it in stage only first, we have to duplicate the collection definition in the kinto.stage.yaml
file, which comes on top of the prod file for the stage server. When happy, move the definition to the prod file and remove the one from the stage file.
I'm also happy to do it for you ;)
Assignee | ||
Comment 2•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
Description
•