MOSIP

Interoperating with MOSIP and E-Signet, OpenSource DPG solutions for National ID and digital identity verification

Watch the video above to see a successful configuration of components that are all explained in this section

Introduction

OpenCRVS integration with MOSIP follows a very similar technical process as followed for configuring integration with any other National ID system.

For registration, the same API endpoints are configured, "in-form authentication and verification" uses QR Code scanning or E-Signet.

In order to make MOSIP integration easier from a back-end perspective, we supply a mosip-api middleware component, which should be deployed in the OpenCRVS stack using a docker-compose configuration. The middleware allows you to configure the required business logic for interacting with the MOSIP Packet Manager API according to your needs.

Detailed flow diagrams

To understand the business process around the technical integration between OpenCRVS and MOSIP that is currently available, refer to this Figjam flow diagram:

opencrvs/mosip library

In order to make life as easy as possible for developers who wish to configure the MOSIP integration, we have abstracted away all the non-customisable logic into an NPM library and created mock servers for both MOSIP and E-Signet.

Release OpenCRVS/MOSIP - v1.8.0 · opencrvs/mosipGitHub

Checkout this repo and follow the README to run the middleware and mocks alongside your local instance of OpenCRVS.

mosip-api middleware

The mosip-api middleware is a critical component that must be deployed. This is explained further in the following sections.

mosip/packages/mosip-api at release-v1.8.0 · opencrvs/mosipGitHub

Example countryconfig

We also provide an example, forked country configuration that uses this library. You can follow exactly how we have configured the full business logic by reading the code.

Release OpenCRVS Countryconfig MOSIP - v1.8.0 · opencrvs/opencrvs-countryconfig-mosipGitHub