Signet
GitHubCommunityWhat's NewChatBot
  • ๐ŸŒeSignet
  • ๐Ÿ”Overview
    • โœจFeatures
      • Signup Portal
    • โš–๏ธPrinciples
    • ๐Ÿ“Standards & Security
    • ๐Ÿ“œLicense
  • ๐Ÿ’ปDevelop
    • ๐ŸฆพTechnology
      • ๐Ÿ“ฆTechnology Stack
      • โš™๏ธComponents - eSignet
      • ๐ŸคณComponents - Signup Portal
      • ๐Ÿ“ฒAPI
    • โš™๏ธConfigure eSignet
      • ACR
      • Claims
      • .well-known
        • jwks.json
        • oauth-configuration
        • openid-configuration
  • ๐ŸŽฎTest
    • ๐Ÿ•น๏ธTry It Out
      • Using Mock Data
      • Register Yourself
      • Integrate with eSignet
    • ๐Ÿ‘จโ€๐Ÿ’ปEnd User Guide
      • Health Portal
        • Login with Biometrics
        • Login with Password
        • Login with OTP
        • Login with QR code (Inji)
        • Knowledge Based Identification
        • Signup and Login with OTP for Verified Claims
    • ๐ŸงฉIntegration Guides - eSignet
      • Authenticator Plugin
      • Key Binder Plugin
      • Audit Plugin
      • Digital Wallet
        • Credential Holder
        • Wallet Authenticator
      • Relying Party
    • ๐Ÿ”Integration Guide - Signup Portal
      • Identity Verifier Plugin
      • Profile Registry Plugin
      • Integration with eSignet portal
  • ๐Ÿ› ๏ธDeploy
    • โ›ด๏ธDeployment Architecture
      • On-Prem Installation Guidelines
    • โš“Local Deployment
      • Mock Identity System
      • Mock Relying Party
  • ๐Ÿ”ŒInteroperability
    • MOSIP
    • Inji
    • OpenCRVS
  • ๐Ÿš€Roadmap and Releases
    • ๐Ÿ›ฃ๏ธRoadmap
      • Roadmap 2025
      • Roadmap 2024
    • ๐Ÿ“–Releases
      • v1.5.1
        • Test Report
      • v1.5.0
        • Test Report
      • v1.4.2
      • v1.4.1
        • Test Report
      • v1.4.0
        • Test Report
      • v1.3.0
        • Test Report
      • v1.2.0
        • Test Report
      • v1.1.0
        • Test Report
      • v1.0.0
        • Test Report
      • v0.9.0
        • Test Report
  • ๐ŸคCommunity
    • Code Contribution
    • Code of Conduct
  • ๐Ÿ“ŒGeneral
    • ๐Ÿ“šResources
    • โ“FAQs
    • ๐Ÿ’กGlossary
Powered by GitBook

Copyright ยฉ 2021 MOSIP. This work is licensed under a Creative Commons Attribution (CC-BY-4.0) International License unless otherwise noted.

On this page

Was this helpful?

Edit on GitHub
Export as PDF
  1. Develop
  2. Technology

Components - Signup Portal

Last updated 4 months ago

Was this helpful?

The image below is a block diagram of the sign up portal comprising various components along with the different layers and external systems.

Signup UI

This is the user interface component of the Signup portal is developed using React JS. Its main functionality is to handle user registration and eKYC verification. Signup UI seamlessly integrates with the UI REST endpoints provided by the signup service. The Signup UI supports multiple languages. Signup UI verifies the OTP before the user registration. A notable feature added in the signup UI is to carry out video-based eKYC verification.

Signup Service

This service is the primary backend spring Java application that incorporates various layers.

  1. Services: This layer defines the services implemented in the signup service. Registration service implements all the business logic related to OTP verification and the registration process. As we currently support a video-based online eKYC verification process, it requires two-way communication between UI and the backend service. To support this we establish a WS connection between signup UI and signup service, WebSocket Handler manages the WebSocket connection. eKYC verification service contains the logic to initiate and manage the eKYC verification transaction.

  2. Rest APIs: This layer exposes REST endpoints for the functionality implemented in the service layer.

  3. Cache Layer: The signup service maintains complete transaction details in the cache. Currently, supports โ€œsimpleโ€ and โ€œredisโ€ cache types.

  4. Plugins: Integration points with external systems are designed to be pluggable, allowing easy integration. The pluggable integration points are as follows:

  5. Reused: Modules from the MOSIP platform and eSignet are reused in the Signup service instead of rewriting the existing logic.

eKYC Verifiers

Trusted claim providers are authorized(depending on policies and regulations) to carry out an identity verification process in which the user is asked to provide proof and prove legitimacy concerning the user's account.

ID Registry:

An ID Registry is a system or database that stores and manages identity information about individuals or entities. An ID Registry is a critical part of digital identity management, acting as a centralized repository for authenticating and verifying the identity of users. In the context of the Signup Portal, the ID Registry could refer to any external system or service that stores user identity information. When a user registers, the Signup Service may interact with an ID registry to validate and store details like the userโ€™s email, phone number, or even government-issued ID, ensuring that the identity is legitimate and unique.

- To create and update user identity data

- Plugin to verify the user identity data, basically the backend for the eKYC verification process.

- For auditing all events

Note: All plugin interfaces are defined in the module.

๐Ÿ’ป
๐Ÿฆพ
๐Ÿคณ
Profile Registry Plugin
Identity Verifier Plugin
Audit Plugin
signup-integration-api
Signup components