#Multiledger io verification#

We always want to ensure we’re providing the latest agent versions to our customers. We upgraded our Orbit Enterprise cloud agent to ACA-Py 0.7.4. We recently wrote a blog post about the main reasons for which we chose AFJ and what excites us about AIP 2.0.ģ Upgraded Enterprise Cloud Agent to ACA-Py 0.7.4 AIP 2.0, builds on AIP 1.0 including how Aries agents can exchange several types of verifiable credentials, including W3C standard verifiable credentials.

AIP 1.0, defines how Aries agents communicate with each other using a single type of verifiable credential, and.

We did this to ensure we move towards AIP 2.0 compliance with our mobile agent. We upgraded our Orbit Edge Mobile Wallet agent to Aries Framework JavaScript (AFJ). This means that a connection to NB Orbit isn’t necessary for the proof presentation to be verified.Ģ Upgraded Mobile Agent to Aries Framework JavaScript (AFJ) We have now changed this process and dropped the forced connection to avoid any federation.

In our previous architecture, we would force a connection between the individual and the platform (NB Orbit) so that the connection-based proof request could happen.

#Multiledger io verification#

This means that the person has credentials in their Edge Wallet (or any other AIP compliant wallet) that they must present to Orbit Enterprise to access their organization’s control panel.Įven though the Orbit Enterprise platform verifies the passwordless access credential, we didn’t want to force a connection between NB Orbit platform and mobile holder – hence a connectionless verification is performed. To act on behalf of an organization, people must have previously established a relationship with the organization, and have had the organization provision them with certain access rights through credential offers. They will manage connections, credential schemas and various functions relating to the issuance and verification of credentials. Users of Orbit Enterprise are people that are acting on behalf of an organization. One of the areas in which we demonstrated connectionless exchanges is through the way passwordless authentications are done to gain access to Orbit Enterprise. įor those interested, we wrote about how we look at connection-based vs connectionless interactions in a recent blog post titled “ Why credential issuance should be holder-driven”. We’ve enhanced the types of verifications that are possible by adding support for Connectionless Exchanges. Since our last product release notes were from Q4 2021, we’re overdue in providing you all with an update.ġ Added Support for Connectionless Exchanges Our work since then has been to move the needle towards AIP 2.0 Compliance for both our Mobile Wallet and Enterprise SSI Cloud Platform.

Towards the end of 2021, we demonstrated AIP 1.0 Compliance of our Orbit Edge Mobile Wallet against the Aries Agent Test Harness (AATH) ( here ). It’s very important to us that we continue aligning our product suite against the many existing and emerging technical standards.Īs we build in new features in NB Orbit, we want to continue sharing these updates with the community. Hence we have committed ourselves to compliance with open source projects which lead to the interoperability of Verifiable Credentials. Īs a company, Northern Block believes in enabling digital identity data for any entity to be exchanged and verified using any platform of choice. The theme behind our product work in the first half of 2022 has been around Interoperability.