Skip to content
A repo for exploring the use of Hyperledger Aries to facilitate decentralised identity services.
TypeScript Shell Dockerfile
Branch: demo-finish
Clone or download

Latest commit

Fetching latest commit…
Cannot retrieve the latest commit at this time.

Files

Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.vscode
docker changed name of acme from faber to acme (fixed typo) Mar 18, 2020
images rest of create credential tutorial Mar 18, 2020
src small updates to support the front-end Nov 13, 2019
.DS_Store image annotation Mar 18, 2020
.dockerignore Updated docker configurations Nov 5, 2019
.gitattributes
.gitignore now runs in docker Nov 7, 2019
LICENSE Update LICENSE Nov 5, 2019
config.json
log.txt presentation requests work Nov 12, 2019
nodemon.json now runs in docker Nov 7, 2019
package-lock.json WIP COmmit on all web containers launching Nov 8, 2019
package.json
readme.md update readme Mar 18, 2020
results.xml
tsconfig.json now runs in docker Nov 7, 2019
tslint.json now runs in docker Nov 7, 2019

readme.md

Aries Cloud Controller Node

Quickstart

Clone the repository locally.

Run in docker:

$ cd ./docker $ sh manage up

If you're worried the set up script has failed because you can't connect, make sure to give this plenty of time. In my case it took ~8 minutes to set up.

In this example we're running a demo with three Agents; Alice, Faber and Acme. We're also running a small ledger network. Configuration details for this set up can be seen inside "docker/manage" and "docker/docker-compose.yml". In this case we use an implementation of Aries which is designed to run an agent as a cloud service. However, this communication can also be managed by smart phone apps (StreetCred). Cloud agents can be interacted with via a web front-end. This can be used to manage communication between Agents. The web front end allows us to create, issue and verify credentials with other parties.

Once the nodes have set up properly, they will be accessible on the following urls;

If you'd like to learn how to interact with Agents via command line, [this blog] (https://www.google.com) is really useful.

Building a Credential Eco-System for Anonymous Verification of Google Account

We'd like users to be able to prove they are eligible for COVID screening without the service provider knowing the identity of the user. We can do this using DID documents, Verifiable Credentials (VCs) and some distributed identity concepts. We have a simple ecosystem to facilitate this which is outlined below;

Step 0 Step 1 Step 2

Let the UN be Alice, Google be Faber and our user be Acme.

Building Relationships Between Cloud Agents

First we need to create some connections to the other nodes in the eco-system. When two Agents connect, they do so with the PeerDID protocol. Each Agent shares a DID document with the other. For each relationship that an Agent has, it creates and shares a unique DID document. In this sense, the Agent assumes a different identity with different key pairs for each entity it interacts with.

Below is the landing page of the cloud-agent. We'll walk through a connection set up using the cloud agent GUI;

Step 0

First, click create/ accept request on the respective agents. Then copy the connection request url into the recipients window. This would usually be done through a QR code.

Step 2

The recipient will be asked whether they accept this connection. Accept the connection.

Step 3

The connection will now appear on the landing page of the Agent who generated the request.

Step 4

Sharing DiD documents with the PeerDID protocol facilitates an encrypted channel. However, at this stage, trust has not been established. Trust is achieved by sharing proofs and proof requests over this channel. In the next step we will define a credential which we can issue and verify.

Defining Credentials

Next we will be creating some credentials. Navigate to the address below and select create.

Step 0

We then fill out the details of our given credential and submit it. The credential is written to the blockchain along with the public DID document of the issuer. We are then redirected to the credential issuer page.

Step 0 s

Issuing Credentials

You can’t perform that action at this time.