Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
tdiesler opened this issue Dec 21, 2022 · 1 comment

Comments

@tdiesler
Copy link
Contributor

tdiesler commented Dec 21, 2022

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: tdiesler/nessus-didcomm#6

@FabioPinheiro
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants