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

Align the DIDComm protocol implementation in the cloud-agent with the DIDComm specification #1508

Open
yshyn-iohk opened this issue Jan 28, 2025 · 0 comments

Comments

@yshyn-iohk
Copy link
Member

yshyn-iohk commented Jan 28, 2025

Is this a regression?

No

Description

All Aried protocols (e.g., issue credentials, present proof, revoke credentials, report a problem, etc.) should be revised according to the DIDCommV2 specification.

Please provide the exception or error you saw

1. Follow the [specification recommendation](https://identity.foundation/didcomm-messaging/spec/#:~:text=body%20%2D%20OPTIONAL.%20The,exist%20when%20receiving) for the`body`property: _to be fully compatible with DIDComm v2.0. It’s recommended always to have this attribute when sending a message, but allow the attribute not to exist when receiving._
2. Alight the internal properties of the `body` between the cloud agent and edge agents for each DIDCommV2 protocol and each message.
Example of the message: issue-credential/3.0/issue-credential

Please provide the environment you discovered this bug in

DEV

Anything else?

Interoperability with other SSI systems and agents needs to align with the specifications and not send unnecessary properties

@yshyn-iohk yshyn-iohk changed the title Align the DIDComm protocol implementation in the cloud-agent with the DIDComm specification (optional body property) Align the DIDComm protocol implementation in the cloud-agent with the DIDComm specification Jan 29, 2025
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

1 participant