Skip to main content

Introduction

One Shot SignOnBoarding with Gui Dizme Use CaseSDK

This document describes a typical customer integration case that covers the integration of the OnBoarding FLOW with the OneGUI ShotDIZME SignSDK 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:

Integrate the GUI Dizme SDK

Before to start with this scenario be sure to correct integrate di Dizme SDK by following the specific documentaztion.

Scenario

It is common to encounter Dizme service integration scenarios where the customer, to provide a specific service, needswant to "ask"integrate the userDizme toSDK demonstrateinside thatan theyown possessMobile particular information.

This translates into a proof for issuing integration.APP.

In this case, the Customer offer tostart the userOnBoardig of the possibilityUser to sign an objectWallet by using theown Userservice Certifiedthat Credentialcan Databe called from their own app and tocomunicate authorize this sign directly fromwith the wallet.SDK to manage callback for response about completition on issuing and verify of the credentials.

Back to top