Hyperledger Aries Cloud Agent - Python

An easy to use Aries agent for building SSI services using any language that supports sending/receiving HTTP requests.

About this fork of ACA-Py

The purpose of this fork is to adapt ACA-Py to work with ATALA prism and sidetree-cardano DID methods, did:prism and did:ada respectively. This development is part of Catalyst funded proposals Interoperability as Growth Driver and Hyperledger-Prism Interoperability.

Take note that this project is in Beta phase and improving is underway. Testing and collaboration are welcomed!

This fork includes the following features:

• Support for did:prism method operations (powered by WAL-CLI)
• Support for did:ada method operations (powered by sidetree-cardano)
• Support for SECP256K1 signatures
• In Memory wallet support for:
  • Create did:prism and did:ada
  • Resolve did:prism and did:ada
  • Update did:ada documment
  • Rotate did:ada keys (pending deveopment to rotate did:prism)
  • Note 1: DID document for did:ada is stored as did metadata
  • Note 2: since recovery is not supported in Aries, sidetree update and recovery keys are merged into one

DEMO ATALA PRISM

Start Alice agent in one terminal:

python ./demo-prism/alice.py

In a second terminal start Faber agent:

python ./demo-prism/faber.py

From the agent's menu you'll be able to:

• Create did:prism and store in ledger and wallet
• Ceate an out of band invitation to other agent
• Establish connection between two agents
• Basic messaging between agents
• Request a credential with issuer and subject are did:prism
• Issue a signed credential with did-prism keys
• Validate credential proof based on public did:prism reseolved on ledger

DEMO SIDETREE-CARDANO

Start Alice agent in one terminal:

python ./demo-sidetree-cardano/alice.py

In a second terminal start Faber agent:

python ./demo-sidetree-cardano/faber.py

From the agent's menu you'll be able to:

• Create did:ada and store in ledger and wallet
• Ceate an out of band invitation to other agent
• Establish connection between two agents
• Basic messaging between agents
• Request a credential with issuer and subject are did:ada
• Issue a signed credential with did-ada keys
• Validate credential proof based on public did:ada reseolved on ledger

Overview

Hyperledger Aries Cloud Agent Python (ACA-Py) is a foundation for building Verifiable Credential (VC) ecosystems. It operates in the second and third layers of the Trust Over IP framework (PDF) using DIDComm messaging and Hyperledger Aries protocols. The "cloud" in the name means that ACA-Py runs on servers (cloud, enterprise, IoT devices, and so forth), and is not designed to run on mobile devices.

ACA-Py is built on the Aries concepts and features that make up Aries Interop Profile (AIP) 1.0, and most of the features in AIP 2.0. ACA-Py’s supported Aries protocols include, most importantly, protocols for issuing, verifying, and holding verifiable credentials using both Hyperledger Indy AnonCreds verifiable credential format, and the W3C Standard Verifiable Credential format using JSON-LD with LD-Signatures and BBS+ Signatures.

To use ACA-Py you create a business logic controller that "talks to" ACA-Py (sending HTTP requests and receiving webhook notifications), and ACA-Py handles the Aries and DIDComm functionality. That controller can be built in any language that supports making and receiving HTTP requests; knowledge of Python is not needed. Together, this means you can focus on building VC solutions using familiar web development technologies, instead of having to learn the nuts and bolts of low-level cryptography and Trust over IP-type Aries protocols.

This checklist-style overview document provides a full list of the features in ACA-Py. The following is a list of some of the core features needed for a production deployment, with a link to detailed information about the capability.

Multi-Tenant

ACA-Py supports "multi-tenant" scenarios. In these scenarios, one (scalable) instance of ACA-Py uses one database instance, and are together capable of managing separate secure storage (for private keys, DIDs, credentials, etc.) for many different actors. This enables (for example) an "issuer-as-a-service", where an enterprise may have many VC issuers, each with different identifiers, using the same instance of ACA-Py to interact with VC holders as required. Likewise, an ACA-Py instance could be a "cloud wallet" for many holders (e.g. people or organizations) that, for whatever reason, cannot use a mobile device for a wallet. Learn more about multi-tenant deployments here.

Mediator Service

Startup options allow the use of an ACA-Py as an Aries mediator using core Aries protocols to coordinate its mediation role. Such an ACA-Py instance receives, stores and forwards messages to Aries agents that (for example) lack an addressable endpoint on the Internet such as a mobile wallet. A live instance of a public mediator based on ACA-Py is available here from Indicio Technologies. Learn more about deploying a mediator here. Coming soon is a Hyperledger Aries Mediator repository that includes a fully configured mediator ready for production deployment using ACA-Py as a dependency.

Indy Transaction Endorsing

ACA-Py supports a Transaction Endorsement protocol, for agents that don't have write access to an Indy ledger. Endorser support is documented here.

Scaled Deployments

ACA-Py supports deployments in scaled environments such as in Kubernetes environments where ACA-Py and its storage components can be horizontally scaled as needed to handle the load.

Example Uses

The business logic you use with ACA-Py is limited only by your imagination. Possible applications include:

• An interface to a legacy system to issue verifiable credentials
• An authentication service based on the presentation of verifiable credential proofs
• An enterprise wallet to hold and present verifiable credentials about that enterprise
• A user interface for a person to use a wallet not stored on a mobile device
• An application embedded in an IoT device, capable of issuing verifiable credentials about collected data
• A persistent connection to other agents that enables secure messaging and notifications
• Custom code to implement a new service.

Getting Started

For those new to SSI, Aries and ACA-Py, there are a couple of Linux Foundation edX courses that provide a good starting point.

• Identity in Hyperledger: Indy, Aries and Ursa
• Becoming a Hyperledger Aries Developer

The latter is the most useful for developers wanting to get a solid basis in using ACA-Py and other Aries Frameworks.

Also included here is a much more concise (but less maintained) Getting Started Guide that will take you from knowing next to nothing about decentralized identity to developing Aries-based business apps and services. You’ll run some Indy apps, ACA-Py apps and developer-oriented demos. The guide has a table of contents so you can skip the parts you already know.

Understanding the Architecture

There is an architectural deep dive webinar presented by the ACA-Py team, and slides from the webinar are also available. The picture below gives a quick overview of the architecture, showing an instance of ACA-Py, a controller and the interfaces between the controller and ACA-Py, and the external paths to other agents and public ledgers on the Internet.

Installation and Usage

An "install and go" page for developers is available if you are comfortable with Trust over IP and Aries concepts. ACA-Py can be run with Docker without installation (highly recommended), or can be installed from PyPi. In the /demo directory there is a full set of demos for developers to use in getting started, and the demo read me is a great starting point for developers to use an "in-browser" approach to run a zero-install example. The Read the Docs overview is also a way to reference the modules and APIs that make up an ACA-Py instance.

About the ACA-Py Admin API

The overview of ACA-Py’s API is a great starting place for learning about the ACA-Py API when you are starting to build your own controller.

An ACA-Py instance puts together an OpenAPI-documented REST interface based on the protocols that are loaded. This is used by a controller application (written in any language) to manage the behaviour of the agent. The controller can initiate actions (e.g. issuing a credential) and can respond to agent events (e.g. sending a presentation request after a connection is accepted). Agent events are delivered to the controller as webhooks to a configured URL.

Technical note: the administrative API exposed by the agent for the controller to use must be protected with an API key (using the --admin-api-key command line arg) or deliberately left unsecured using the --admin-insecure-mode command line arg. The latter should not be used other than in development if the API is not otherwise secured.

Credit

The initial implementation of ACA-Py was developed by the Government of British Columbia’s Digital Trust Team in Canada. To learn more about what’s happening with decentralized identity and digital trust in British Columbia, a new website will be launching and the link will be made available here.

Contributing

Pull requests are welcome! Please read our contributions guide and submit your PRs. We enforce developer certificate of origin (DCO) commit signing — guidance on this is available. We also welcome issues submitted about problems you encounter in using ACA-Py.

License

Apache License Version 2.0