Introduction
One Shot Sign with Dizme Use Case
This document describes a typical customer integration case that covers the integration with the One Shot Sign Service of InfoCert.
Setting up your SERVICE on Dizme Studio
Before your backend application can use Dizme Api you need to configure a service on your Dizme Studio instance. Given the asynchronous nature of the Dizme Stack (DARS) services, the integrating application will have to set up REST services on which it will receive callbacks. Some of the callbacks refer to the three main operations and are:
-
notify connection: confirmation of new successful connection of a new wallet
-
confirm verify : Successfully confirmed verification confirmation.
-
confirm issue: credential release confirmation completed successfully.
The endpoint and path of these callbacks can be configured in the Services section of Dizme Studio.
Callback specifications can be found on the following page:
Scenario
It is common to encounter Dizme service integration scenarios where the customer, to provide a specific service, needs to "ask" the user to demonstrate that they possess particular information.
This translates into a proof for issuing integration.
In this case, the Customer offer to the user the possibility to sign an object by using the User Certified Credential Data and to authorize this sign directly from the wallet.