-
Notifications
You must be signed in to change notification settings - Fork 9
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
feat: Added API to delete connection, and added patch for multi-tenancy OOB connection #232
base: develop
Are you sure you want to change the base?
feat: Added API to delete connection, and added patch for multi-tenancy OOB connection #232
Conversation
… oob connection Signed-off-by: Sagar Khole <sagar.khole@ayanworks.com>
Can we also have a short description of the issue that the patch is solving? |
Signed-off-by: Sagar Khole <sagar.khole@ayanworks.com>
8af64b8
to
39a53f5
Compare
|
- .returnWhenIsConnected(connectionRecord.id, { timeoutMs }) | ||
- .then((connectionRecord) => this.emitWithConnection(outOfBandRecord, connectionRecord, messages)) | ||
- .catch((error) => { | ||
+ // this.connectionsApi |
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.
+ // this.connectionsApi | |
+ Remove the commented code if not necessary |
@sagarkhole4 if |
Description
When issuing credentials using the out-of-band protocol with connection reuse disabled or when establishing a new connection, the connection gets successfully established, but the credentials remain in the request-sent state indefinitely.
This issue does not occur when reusing an existing connection. In such cases, the credential issuance process transitions to the appropriate final state as expected.
Delete Connection Functionality:
Patch for Multitenancy OOB Connection:
Issue created on credo-ts Clicl here