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.

Sign up for GitHub

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

Jump to bottom

AATH: OOB #678

Open
Patrik-Stas opened this issue Dec 1, 2022 · 2 comments
Open

AATH: OOB #678

Patrik-Stas opened this issue Dec 1, 2022 · 2 comments
Assignees
@mirgee
Labels
AATH

Comments

@Patrik-Stas
Copy link
Contributor

@Patrik-Stas Patrik-Stas moved this to Backlog in aries-vcx Jan 11, 2023
@mirgee mirgee self-assigned this Feb 27, 2023
@mirgee
Copy link
Contributor

mirgee commented Feb 28, 2023 •
edited
Loading

Work on this was postponed as AATH OOB test cases (excluding DID Exchange tests) rely on connectionless exchange outlined in RFC0496 (where RFC0056 is also relevant), which is currently not implemented in aries-vcx.

@bobozaur
Copy link
Contributor

This should get resolved with the messages crate refactor -> the OOB invitation message should encapsulate any JSON value in the attachment, including an AriesMessage. Maybe the question remains on how to determine that the attachment should be deserialized to a message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mirgee mirgee

Labels
AATH
Projects
aries-vcx
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Patrik-Stas @mirgee @bobozaur