Hyperledger Foundation Hyperledger Global Forum 2022, 6 Oct 2022

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Demo: Aries ACA-Py Controllers: One Agent, Three Web Stacks - Akiff Manji, Petri Dish Development

Description

Demo: Aries ACA-Py Controllers: One Agent, Three Web Stacks - Akiff Manji, Petri Dish Development

Aries agents are designed to perform specific functions that are agnostic and separate from the application business logic of Aries-based SSI solutions. Business logic is instead meant to be placed in controllers that interface with agents. This talk will demonstrate how easy it is to deploy controllers that run on top of an Aries cloud agent built with ACA-Py. Akiff will deploy controllers in three different web frameworks (C#, Node.js and Angular) that can talk with each other and allow for differing and customizable use-cases.

Sessions Details & Slides (if available): https://sched.co/14H45
Access All Sessions: https://events.linuxfoundation.org/hyperledger-global-forum/program/schedule/
----
Hyperledger – Open Source Blockchain Technologies

Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use

Discord: https://discord.gg/rVCn4j7UFd
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory

Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter

Follow-us on Twitter @Hyperledger

Learn about Hyperledger Membership: https://www.hyperledger.org/about/join

#Hyperledger #Blockchain
License
Creative Commons Attribution license (reuse allowed)

A

B

I guess we can get started because it's uh 15 minutes on the DOT, so welcome everybody to the first demonstration at the hyperledger global forum here in Dublin and welcome everybody who's online, whoever you are in the world, so my name is akif. My company's petri dish, development, I work as a consultant and I'm going to be demonstrating the Aries occupy controllers uh using different web stacks.

B

So before we talk about what controllers are, let's quickly talk about acupai um or Aries, Cloud agent python, since occupy is the basis for what controllers are built on so occupy is an Aries implementation written in Python. Its primary use case is to enable cloud-based, verifiable credential Solutions, like Enterprise web wallets, and hence the name Cloud agent.

B

Occupy implements Aries protocols for issuing, holding and proving verifiable credentials, and it enables the trust over IP model that you see here and you'll see frequently. uh So every component of this truss triangle or diamond is enabled by occupy. So you can stand up occupy for issuing for verifying for publishing, schemas and credential definitions on onto ledgers. So it has a wide support for a lot of use. Cases.

B

So acupai is meant to be consumed, as a service controllers are applications that function as the business Logic. The controller simply executes Aries protocols by calling a rest API exposed by occupy, and the controller can also listen to async events through web hooks. So on the right here, this is kind of like the rest response, request response, and then this would be web hooks.

B

So this is a really simple setup with the server-side framework, such as node or net, and the application UI would be built in the controller and it would simply be making requests to the Occupy agent that runs standalone.

B

So here's another setup with this single page application Frameworks, something like angular reactor view, so this would typically require an additional microservice to handle web hook callbacks, because aquapi can't directly call back to the browser. So you could have a setup like this.

B

um It also supports multi-tenancy, meaning that one occupy instance can securely manage multiple agents. So we often refer to this as an agency, where each controller would create a sub-wallet, that's isolated from all the other tenants, and then it would use a token, a JWT to make secure requests to each of the tenants Within the agency, so I'm going to show you a quick demonstration of a few controllers that I built that use occupy in the background.

B

So some of you may be familiar with the Alice Faber Acme interaction. So in this case, Alice is a a graduate from Faber college and she wants to apply for a job at Acme Inc. So Faber is going to issue Alice a degree credential um and then Acme is going to ask Alice to present a proof of her graduation at accredited college for employment and then using that information. If acne approves, then they can also issue an employee credential to Alice.

B

So this is the kind of setup that we have. There are technically three different occupy instances, but they're they're, one Aries framework, so Alice is going to be written in angular favors, written in.net and Acme is uh written with node.js.

B

So it's some I'm just going to stand up the uh the demo here so, as you can see,.

B

So each one of these, these Services, is just making a simple request. A rest API request to the agents writing in the background.

B

So while this is standing up.

B

So, in the background, what's happening is Faber and Acme are going to create a public did they're going to register it onto this local Ledger that I have running, and then Faber is also going to publish a schema and a credential definition for the degree credential so that it can then issue that to Alice.

B

B

So here I have Alice stood up, I have Acme stood up and I think favors ready to go so once again um occupy exposes a rest API. So you can access this directly um through each of the agents, but let's go ahead and create a connection request for Alice to connect to so Faber is going to create a new invitation.

B

So all we're doing is we're making a call to occupy using the rest API and, let's suppose, that it exposes this invitation through some kind of QR code or something that Alice would connect to or even a link.

B

So Alice is going to accept that connection and once it does, it has a active connection to Faber.

B

Favor then has already published a schema for the degree and it's created a credential definition. So now I can go ahead and issue a credential, so so Alice, it's already connected to. We select our schema and credential definition, and this is the attributes of the credential that it will issue to Alice.

B

So once we do that- and uh we can see that Alice has been issued a Prudential here so now, Alice wants to apply for a job.

B

So now Acme is going to create an invitation for Alice to connect you so that she can prove her credentials.

B

So Alex is going to accept the invitation to Acme okay. So it's done that and so now Acme is going to create a proof request.

B

So it's connected to Alice. Now it needs to have the credential definition ID and suppose that this is publicly available somewhere, but we're just going to copy it from Faber.

B

And so here there's a number of different attributes. It's requesting so uh Acme wants to know the name, the date that the degree was issued, what type of degree and then it can also request that you know Alice has to be over a certain age, but we're gonna skip that one.

B

It's a little bit challenging to do this with the with one hand, oops.

B

So proof has been requested.

B

Palaces received that proof request and then hopefully, if everything works in the background, acupai verified the proof and uh Acme sees that it's been verified here, so these controllers took less than a day to write each it's pretty fast to to write something like this, and this just shows how easy like occupy is to to stand up some kind of UI in front of it. So um that's a that's the demo there.

B

um If you'd like to learn more, the QR code will take you to the acupai controllers repo.

B

um We also have a Discord chat if anybody's really interested in learning about Aries Cloud engine Python, and we have a really nice, diverse, community and active community and in this so yeah any questions.

B

uh In terms of a UI not really but the rest.

A

B

So that was business partner agent, yeah.

B

It's it's just a degree schema that was published when we stand up the agent.

B

Yeah, so the schema and the credit def are published on a local ledger, so I can I, have it running and I can probably show you.

B

So if I go to The Domain here, and so you can see like that's the crowd depth that was created and then that's the schema that was created and that was that was published right now. When I, when I stood up the agent.

B

uh No I believe you need to have the ledger to at least publish schemas and cred defs.

A

B

um Yeah and there's another project called traction that uh is, is for creating a multi-tenant type of solution um and I believe they have some UI as part of that, but I think they're, also using business partner agent as part of their UI they're, not.

A

A

B

Yeah, so there's there's a number of different projects that uh people have built Solutions around this so anyways. um The purpose of this was just to really showcase how easy it is if you want to build your own, your own application um in the next demo. Actually right after this we're going to be showcasing um the mobile wallet that we've been working on bifold and that's uh that should be an interesting one to look at too so.

A

B

To the time yeah, that's right, I wrote this.

B

It was a fun project. Yeah I wrote this before I started with their team, so yeah.

A

B

Yeah Yeah, so basically I just have a number of services here. So so, for example like in the in the in.

A

B

Angular application, I just have an agent service, and all it's doing is it's making HTTP requests now if I wanted to, I could also receive web hooks through some other microservice. That I would specify as an endpoint to occupy, and then I could use like web sockets to push information back to like to my application here. The cool thing about using something like.net or node.js is that's kind of. You can do that right out of the box. So it's a simpler sort of architecture to set up but yeah.

B

That's, basically it I'm just having I have these services that call occupy through through rest, the rest API.

B

All right so yeah I look forward to the the next presentation. Then.