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.
Add as needed the additional endpoints as needed to support the use of ACA-Py with an HSM in an enterprise environment.
Add the ability for (at least) a verifiable credential issuer to publish an OCA Bundle that can be consumed by a Wallet and a Verifier.
In preparation for Version 1.0.0 of ACA-Py, an assessment of the [AATH](https://aries-interop.info) tests run between ACA-Py and the other Aries Frameworks (especially Aries Framework JavaScript) should be conducted, and additional...
To implement full support for AIP 2.0, we need to add support for [RFC0317 Please Ack](https://github.com/hyperledger/aries-rfcs/tree/main/features/0317-please-ack) to ACA-Py. The feature needs to support both types of requested ACKs -- `RECEIPT`...
ACA-Py seems to be permissive, in a certain sense, with the format that a base64 attachment payload can take: [`b64_payload = unpad(set_urlsafe_b64(self.base64, True))`](https://github.com/hyperledger/aries-cloudagent-python/blob/main/aries_cloudagent/messaging/decorators/attach_decorator.py#L426). However, this still enforces that the message...
The [DIDComm/DID doc conventions](https://github.com/hyperledger/aries-rfcs/blob/master/features/0067-didcomm-diddoc-conventions/README.md#service-conventions) for services state that `recipientKeys` and `routingKeys` are arrays of DID key references, rather than arrays of raw key values.
Verification method references in the did doc implementation are currently [objects](https://github.com/hyperledger/aries-cloudagent-python/blob/main/aries_cloudagent/connections/models/diddoc/diddoc.py#L137) with a `type` member and a `publicKey` member (a did url), whereas in the spec a verification method reference...
When creating a peer DID doc for DID exchange, it should have the `peer` DID method.
AcaPy should be using the Aries RFC media types rather than `application/ssi-agent-wire`.
The service type should be `did-communication` rather than `IndyAgent` in DID Exchange.