Currently, Unprotected has https://www.rfc-editor.org/rfc/rfc7515#section-4.1 claims, and Protected just wraps these claims.
pub struct Protected {
pub crit: Option<Vec<String>>,
pub nonce: Option<Bytes>,
pub b64: bool,
pub oth: Unprotected,
}
pub struct Unprotected {
pub alg: Option<Signing>,
pub jwk: Option<Jwk>,
pub kid: Option<String>,
pub x5c: Option<Vec<Bytes<Box<[u8]>, Base64>>>,
pub x5t: Thumbprint,
pub typ: Option<String>,
pub cty: Option<String>,
}
I think the naming is somewhat confusing, at least to my understanding since Unprotected data may be protected. Maybe it would be better to move the Unprotected contents to a Common struct and reference it from both Protected and Unprotected?
Also not sure how this should interact with JWEs since they have the same headers. Would jose_alg be better named jose_common or something like that?
Currently,
Unprotectedhas https://www.rfc-editor.org/rfc/rfc7515#section-4.1 claims, andProtectedjust wraps these claims.I think the naming is somewhat confusing, at least to my understanding since
Unprotecteddata may be protected. Maybe it would be better to move theUnprotectedcontents to aCommonstruct and reference it from bothProtectedandUnprotected?Also not sure how this should interact with JWEs since they have the same headers. Would
jose_algbe better namedjose_commonor something like that?