fix: didx request cannot be accepted #1881
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi everyone,
this PR fixes a few problems which were apparently introduced by #1710:
A didx request which is received in response to an explicit oob invitation cannot be accepted because the state of the corresponding connection record is not updated to
'request-received'
The admin api incorrectly indicates that the
/out-of-band/receive-invitation
endpoint returns aConnRecord
instead of the newOobRecord
(which is also why theOobRecord
is not included in theswagger.json
)@TimoGlastra: maybe you want to take a look to make sure I didn't break the connectionless exchange feature by saving the updated connection record?