You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DID Comm specs we can read: All three DIDComm message formats — plaintext, signed, and encrypted — can be correctly understood as more generic [JWMs (JSON Web Messages)](https://tools.ietf.org/html/draft-looker-jwm-01)
Although there are a lot of reference to JWS in the DID Comm specification
The problem is that the signed message looks more like the examples in JWS and the JWM.
Because JWS uses the JWS Unprotected Header to have the kid and JWM uses JWS Protected Header.
JWM does not have signatures.header
We need to fix all examples is make JWM.
But JWM document is an Expired Draft. So I'm not fully convinced this is the best solution
The DID Comm specs we can read:
All three DIDComm message formats — plaintext, signed, and encrypted — can be correctly understood as more generic [JWMs (JSON Web Messages)](https://tools.ietf.org/html/draft-looker-jwm-01)
Although there are a lot of reference to JWS in the DID Comm specification
Links:
DID Comm specs signed examples
JWM draft
JWS RFC7515
The problem is that the signed message looks more like the examples in JWS and the JWM.
Because JWS uses the JWS Unprotected Header to have the
kid
and JWM uses JWS Protected Header.Ex from the DID Comm specs:
The text was updated successfully, but these errors were encountered: