decentralized-identity / didcomm-messaging

https://identity.foundation/didcomm-messaging/spec/
Apache License 2.0
161 stars 56 forks source link

Clarify "json": "<json of protocol message>" as input for encoding example #423

Open tdiesler opened 1 year ago

tdiesler commented 1 year ago

Is the above attachment content really valid? (i.e. a string value for type json) If not, Base64 URL Encoded value cannot be right.

didcomm-jvm does not accept it

CrossRef: https://github.com/tdiesler/nessus-didcomm/issues/6

FabioPinheiro commented 1 year ago

There is no attachment above. Are you talking about something like this?

{ 
  "id":"...",
  "attachments": [
     {"data": {"json":"just a json string"}}
   ]
 }

We are assuming this is a valid message.