Implement the JWE metric type
Categories
(Data Platform and Tools :: Glean: SDK, enhancement, P1)
Tracking
(Not tracked)
People
(Reporter: mdroettboom, Assigned: brizental)
References
Details
Attachments
(5 files)
Now that bug 1634468 is approved, we can proceed with the implementation as designed in the document
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
How far should I go with the validation for each element of the JWE? What I am checking right now:
- I check the whole value has 5 elements separated by
.
(thus, I also check that we have 4.
); - I check that each element has a maximum of 1024 characters;
- I check that each element is valid BASE64URL.
With this, a string such as "...."
validates correctly, which doesn't seem right. Or is that good enough?
Should I be validating each field separately, each having it's own constraints?
Comment 2•5 years ago
|
||
(In reply to Beatriz Rizental from comment #1)
With this, a string such as
"...."
validates correctly, which doesn't seem right. Or is that good enough?
I believe that the JWE spec does not allow for all the fields to be empty. If that's the case, I'd only add a check for that.
Assignee | ||
Comment 3•5 years ago
|
||
If I understand the spec correctly, only header and cipher_text must not be empty. I'll add a check for that.
Comment 4•5 years ago
|
||
Comment 5•5 years ago
|
||
Assignee | ||
Comment 6•5 years ago
|
||
Assignee | ||
Comment 7•5 years ago
|
||
Assignee | ||
Comment 8•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
Description
•