aries-cloudagent-python icon indicating copy to clipboard operation
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.

Results 315 aries-cloudagent-python issues
Sort by recently updated
recently updated
newest added

This PR enables the Schema class of a model to determine the default `unknown` behavior. Without this, if you have a schema where you expect extra values to be present,...

As mentioned in PR #1864, it is not currently possible to use `credentialStatus` within JSON-LD credentials. Whichever version of the credential status is implemented, it would be nice to be...

For jwt tokens that have been created without the iat field, they will no longer be considered valid and the profile cannot be retrieved. The offending code is located here:...

As part of #1859, I have made it so the coordinate-mediation protocol uses did:key representation. Apologies that this took as long as it did. Implementing this impacted more of ACA-Py...

We need to update from Python 3.6, and so need a plan to do so. PR #1854 has been created to start the process. We discussed this at the [ACA-Pug...

Hi, I have set up 2 ACA-PY agent containers in docker. However, they fail to communicate and build connections with each other although I have set the endpoint using >...

The existing AnonCreds handlers in ACA-Py handle AnonCreds objects that are rooted in Indy. We would like to make the AnonCreds implementation in ACA-Py VDR agnostic -- at least as...

Just like we want to have a generic DID Resolution capability in ACA-Py such that we can resolve any DID (or at least the ones we are willing to resolve),...

[+] Building 1.6s (16/16) FINISHED => [internal] load build definition from Dockerfile.run 0.0s => => transferring dockerfile: 41B 0.0s => [internal] load .dockerignore 0.0s => => transferring context: 34B 0.0s...

### Environment - Aca-py 0.7.4 - Askar - indy credx 0.3.1 ### Situation 1. A holder received a credential that does **not support revocation**. 2. A holder tried to check...