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

fix: multi-use OOB invitations #26

Merged
merged 1 commit into from
Nov 17, 2022
Merged

fix: multi-use OOB invitations #26

merged 1 commit into from
Nov 17, 2022

Conversation

dbluhm
Copy link
Member

@dbluhm dbluhm commented Nov 17, 2022

@mepeltier see if this fixes your issues! 🙂

Signed-off-by: Daniel Bluhm <dbluhm@pm.me>
Copy link
Contributor

@mepeltier mepeltier left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll give it a shot, thanks!

@mepeltier mepeltier merged commit 03d071b into main Nov 17, 2022
@dbluhm dbluhm deleted the fix/multi-use-oob-events branch November 17, 2022 16:16
@dbluhm
Copy link
Member Author

dbluhm commented Nov 17, 2022

As an aside, I noticed that the invitation message ID was not getting set on the newly created connection record. I had to use the invitation key as the correlation back to the original OOB invite. It works but I think it would be semantically more precise for the invitation message id to be set on the connection and use that. @mepeltier perhaps we should look at tweaking this behavior in ACA-Py? Maybe it's already something in main; I ran against 1.0.0 rc0.

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

Successfully merging this pull request may close these issues.

2 participants