ID Repository

Overview

ID Repository contains the records of identity of an individual, and provides API based mechanism to store, retrieve and update identity details by other MOSIP modules. ID Repository is used by Registration Processor, ID Authentication and Resident Services.

Services

ID Repository module consists of the following components:
  1. 1.
    Identity service
  2. 2.
    VID service
  3. 3.
    Credential service
  4. 4.
    Credential Request Generator service
  5. 5.
    Credential Feeder
  6. 6.
    Salt generator

Identity service

  • Stores, updates, retrieves identity information and also to
  • Retrieves and updates UIN status.
Identity service uses Biometric SDK (server) to extract templates from provided biometric data.
Above is the entity relationship diagram illustrated for Identity service. NOTE: The numbers do not signify sequence of operations or control flow. Arrows indicate the data flow.
  1. 1.
    Key Manager encrypts/decrypts data.
  2. 2.
    Credential request generator issues credentials for new/updated UIN data.
  3. 3.
    Object Store stores/retrieves biometrics and demographic documents.
  4. 4.
    All demographic data of UIN and references to biometric and demographic files stored in object store are stored in mosip_idrepo DB.
  5. 5.
    Partner management service retrieves online verification partners to issue credentials.
  6. 6.
    Audit logs are logged into Audit Manager.
  7. 7.
    Biometric SDK extracts the templates for input biometric data.
  8. 8.
    Auth Adapter integrates with KeyCloak for authentication.
  9. 9.
    Masterdata service retreives Identity schema based on input schema version.
  10. 10.
    WebSub publishes events related to UIN updation and auth type status updates.
  11. 11.
    Kernel ID generator generates UIN.
  12. 12.
    VID service fetches the list of VIDs associated with UIN to issue credential of update UIN and to create and activate draft VID.

VID service

VID Service provides functionality to create/update Virtual IDs mapped against an UIN. It also provides the facility to update status of VID. VIDs are created based on the VID policy defined in the configuration.
  1. 1.
    Key Manager encrypts/decrypts data.
  2. 2.
    Credential request generator issues credentials for new/updated UIN data. 3 All VID related data is stored in mosip_idmap DB.
  3. 3.
    Partner management service retrieves online verification partners to issue credentials.
  4. 4.
    Audit logs are logged into Audit Manager.
  5. 5.
    Auth Adapter integrates with KeyCloak for authentication.
  6. 6.
    WebSub publish events related to VID updation.
  7. 7.
    Kernel ID generator generates VID.
  8. 8.
    Identity service checks the status of UIN to create VID.

Credential service

  1. 1.
    Key Manager encrypts/decrypts data and also used to sign data.
  2. 2.
    WebSub subscribes to get notifications related to credential status from IDA.
  3. 3.
    DataShare creates datashare url for sharable attributes.
  4. 4.
    Identity service retrieves identity data for UIN/VID.
  5. 5.
    Partner management service retrieves policies related to credential type and also retrieves policy for bio-extraction.
  6. 6.
    Auth Adapter integrates with KeyCloak for authentication.

Credential types

A credential can be defined as any document, object, or data structure that vouches for the identity of a person through some method of trust and authentication. Simply put, a credential is the thing that a person presents—in person or remotely—to say "this is who I am." The types of credentials issued in an ID system vary along multiple dimensions, depending on whether they are physical (i.e., they must be physically carried by a person in order to use them), or digital (i.e., they are machine readable and therefore can be used in a digital environment).
A credential type essentially maps to partner and data share policy.
Default credential types provided as part of sandbox deployment are given below:
  1. 1.
    auth: Represents individual's data shared with Online Verification Partners (further used for Authentication and eKYC).
  2. 2.
    qrcode: qrcode type is used for qrcode partners to issue qrcode related credential data.
  3. 3.
    euin: It is used to issue credential data to partners who wish to download euin card using euin policy.
  4. 4.
    reprint: Reprint auth type is used for issuing credential information to reprint partners.
  5. 5.
    vercred: To issue verifiable credentials to partners, vercred credential type is used.
New credential types may be defined as per needs of a country.

Credential request generator service

This service creates request for credential issuance.
  1. 1.
    Key Manager encrypts/decrypts data.
  2. 2.
    Auth Adapter integrates with KeyCloak for authentication.

Credential feeder

This job will feed the existing UIN/ VID identity information to newly deployed IDA instance.

Salt generator

This is a one-time job that populates salts that are used to hash and encrypt data for Identity and VID services. This job must be executed before deploying these services. The following tables are populated:
  • uin_hash_salt in mosip_idrepo DB.
  • uin_encrypt_salt in mosip_idmap DB.
In MOSIP sandbox, the job is run here.

Developer Guide

To know more about the developer setups, read:

API

Source code

Export as PDF
Copy link
Edit on GitHub
On this page
Overview
Services
Identity service
VID service
Credential service
Credential types
Credential request generator service
Credential feeder
Salt generator
Developer Guide
API
Source code