aries-cloudagent-python
aries-cloudagent-python copied to clipboard
Hyperledger Aries Cloud Agent Python (ACA-Py) is a foundation for building decentralized identity applications and services running in non-mobile environments.
The issue is detailed in the [OpenWallet JavaScript Agent] in [this comment](https://github.com/openwallet-foundation/agent-framework-javascript/pull/1638#issuecomment-1872563156) and in [Issue 1625](https://github.com/openwallet-foundation/agent-framework-javascript/issues/1625) \: If you have a clustered environment, it is possible that a message arriving...
While testing OOB webhook notifications for connection process, I noticed that OOB "deleted" event is not present after connection becomes active, but "done" event is in place (single use invitation)....
With the following setup [auto flags enabled]: - multiledger config - 2 different ledger networks with associated endorser agents - author role tenant - First step, able to create and...
I'm using aca-py 0.8.2 as issuer and holder agent. When holder agent received out-of-band invitation with credential-offer attachment from issuer, holder agent can not proceed attachement because new connection is...
There is a ***mismatch*** in fields. `invi_msg_id` is returned from the `/out-of-band/create-invitation` POST, but it is returned in webhooks under the `connections` topic as `invitation_msg_id`. > > FROM API: >...
When we receive a DID Document in Connections or DID Exchange, we store the document. The document is never deleted after the associated connection is deleted. We should do that.
We are looking to add support for DID Rotation in ACA-Py. At minimum we want to be able to accept a DID Rotation request for an existing connection. Next level...
This PR is an attempt to make a start point of discussion how to implement the `please_ack` decorator support in ACA-Py. The PR contains initial version of the document that...
Scenario: - we have 2 tenants created on a multitenant agent - both agents have a published, public did - agent 1 creates invitation with `use_public_did = True`, and `auto_accept...
In https://github.com/hyperledger/aries-acapy-plugins/pull/47, we implemented verification of additional signature types. The current `/wallet/jwt/verify` endpoint only accepts Ed25519 signatures right now. It should be (was, in the plugin) pretty straightforward to verify...