-
Notifications
You must be signed in to change notification settings - Fork 516
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
Allow public invites for alice/faber demo #1574
Allow public invites for alice/faber demo #1574
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1574 +/- ##
=======================================
Coverage 95.78% 95.78%
=======================================
Files 528 528
Lines 32491 32491
=======================================
Hits 31120 31120
Misses 1371 1371 |
Hmm...I ran this:
|
You don't need to add a new parameter to faber, the |
So it works, but each time I do a new invitation, I get a new connection on both sides. That means that reuse is not being used, which is the goal. Alice should be responding with a "reuse" message, and her "new" connection should be removed. Likewise on Faber -- once she responds with the reuse, the hanging connection should be removed. This (pretty likely :-) ) works because there was a follow up tweak to DID Exchange to do the clean up after someone tried this out. Thoughts? |
I think the reuse should be automatic, handled by ACA-Py, but am not certain how it works. |
Also, I noticed that the "their_public_did" item on the connection object was not set, which is a bit odd. Not sure why it wouldn't be, but I think that is a pre-requisite for "reuse" on a connection. |
I believe the auto-reuse only works when you use public DIDs for connections, which the demo is not doing |
I guess it depends on the intent, I though we were just trying to unblock Peter (issue #1571 where he is using the API). If we want to configure alice/faber to use connection reuse for the demo then there is more work required. Let me know ... |
Let's leave it for now. Peter's goal is to enable connection reuse, so that's really what we are after. I think it would be nice to have the demo optional support connection reuse, so it would have an optional parameter, making it easy to see what the controller has to do to support reuse. How about we leave this as a draft PR and when you get a chance, you can update it? I'm hoping it is a pretty small change. |
Sure that works, I've converted the PR to draft. |
Signed-off-by: Ian Costanzo <[email protected]>
Signed-off-by: Ian Costanzo <[email protected]>
Signed-off-by: Ian Costanzo <[email protected]>
Signed-off-by: Ian Costanzo <[email protected]>
0049c4b
to
7fcdfaf
Compare
Signed-off-by: Ian Costanzo <[email protected]>
Fixed demo - run with (Alice will always try to reuse connections if possible.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alice
reuses the existing connection as intended.
Signed-off-by: Ian Costanzo [email protected]
Addresses #1571
Note - added a
--reuse-connections
parameter to faber - this will trigger faber to use a public did in the didexchange connection (and alice will always "reuse connection" if possible) and the connection indeed gets reused, however right now there are no webhooks for the "reuse" messages so the alice/faber controllers are getting hung ...