LogoLogo
CommunityLicense
1.0.0
1.0.0
  • 🏠Home
  • 🏢Architecture
  • 📋Registration
    • Registration Interfaces
      • Mobile Registration App
      • Self Service Portal
      • API Interface
    • ID Verification
    • Registry
  • 🅿️Program Management
    • Eligibility Assessment
    • Enrolment
    • Deduplication
    • Disbursement Cycles
    • Entitlement
    • Verifiable Credentials
  • 💵Payment Management
    • Payment Cycles
    • Payment Batches
    • Payment Manager
    • Payment Types
      • In Account
      • Voucher
      • Cash
      • In Kind
    • Payment Rails
    • Accounting
      • Accounting
      • Reconciliation
      • Reports
  • Notifications
  • 📊Monitoring and Reporting
  • ⛓️Workflows
    • Cash grant scenario
    • On-Demand Assistance
  • 🔗Integrations
    • Mojaloop Integration
    • MOSIP Integration
      • ODK MTS Connector
      • Registry MTS Connector
      • Integration with e-Signet
  • ↔️API
  • ⚒️Testing
  • 👥Community
    • Contributing
    • Code of Conduct
  • 📗License
  • Guides
    • 📔How-To Guides
      • Create Program
      • Configure Proxy Mean Test
      • Create User and Assign Role
      • Create ODK Form
      • Create Portal Form
      • Provide Form Access to Field Agent
      • Download Form on ODK Collect
      • Register Offline
      • Self Register Online
      • Create MTS Connector
        • Create ODK MTS Connector
        • Create OpenG2P Registry MTS Connector
      • Enrol Registrants into Program
      • Create and Approve Disbursement Cycle
      • Prepare and Send Payment
      • Create Payment Manager under Program
      • Create Payment Manager Types
        • Create Payment Hub EE Payment Manager
        • Create Payment Interoperability Layer Payment Manager
        • Create Default Payment Manager
      • Create Eligibility Manager under Program
      • Create Eligibility Manager Types
        • Create Default Eligibility Manager
        • Create ID Document Eligibility Manager
        • Create Phone Number Eligibility Manager
      • Create Deduplication Manager under Program
      • Create Deduplication Manager Types
        • Create ID Deduplication Manager
        • Create Phone Number Deduplication
      • Create Notification Manager under Program
      • Create Notification Manager Types
        • Create SMS Notification Manager
        • Create Email Notification Manager
        • Create Fast2SMS Notification Manager
      • Send Notification to Individual Registrants
      • Configure ID Types
      • Map ODK Form
      • Integrate with MOSIP e-Signet
      • Map Self Service Portal Form
      • Install WireGuard App And Activate Tunnel
      • Install SmartScanner App
      • Submit Reimbursement Using the Service Provider Portal
    • 📙Documentation Guides
      • Creating Diagrams
      • Writing Guidelines For How-To Guides
    • 👩‍💻👩💻 👩💻 👩💻 👩💻 👩💻 Developer Zone
      • Getting Started
      • Technology Stack
      • About Github Repositories
        • openg2p-registry
        • openg2p-program
    • 📘Deployment Guide
      • Deployment on Kubernetes
        • K8s Cluster Requirements
        • K8s Cluster Setup
        • Rancher Server Setup
        • NFS Server Setup
        • SSL Certificates using Letsencrypt
      • Access to Deployed Setup
      • Post Install Configuration
      • Packaging OpenG2P Docker
Powered by GitBook
LogoLogo

Copyright © OpenG2P. This work is licensed under Creative Common Attribution (CC-BY-4.0) International license unless otherwise noted.

On this page
  • Overview
  • Features
  • Configuration
Export as PDF
  1. Integrations
  2. MOSIP Integration

Registry MTS Connector

PreviousODK MTS ConnectorNextIntegration with e-Signet

Last updated 2 years ago

Overview

Registry MTS Connector (RMC) is an Odoo addon that fetches against any record in the registry by calling (MTS) and stores the same in the registry.

Features

  • Generates MOSIP token against the OpenG2P registry by calling .

  • Uses callback delivery type of MTS

  • Completely asynchronous execution

  • OpenG2P can schedule a daily job to fetch the delta for the day

  • A manual import feature will also be provided

  • Removes VID if MOSIP Auth Token is generated

Configuration

Property
Configuration

Name

A string to identify the connector

URL to reach MTS

URL for MTS API

MTS Input type

OMC option could be proceeded by selecting OpenG2P Registry.

Mapping

MTS Field mapping as required by the API. Please refer to MTS Documentation. Format of Mapping would be JSON.

Output Type

MTS-C only supports JSON output type of MTS.

Output Format

Delivery Type

Currently supporting only "Callback". Callback feature can be used to make MTS do a submission of results onto an API within Odoo. The output formatting will help in making the desired input for the api.

Job Type

MTS-C provide both recurring and one time execution. Recurring can be configured to do continuous pull from the ODK over MTS.

MOSIP Language

Mosip language setup. Default is eng.

Interval in minutes

Interval at which the MTS-C job runs.

Filters to apply to Registry

List of fields to be used

List of fields which will be supplied as auth data. This field list may be a superset of fields required for auth as it may contain data required by the callback API. This list should be a valid JSON string array.

Callback URL

A URL endpoint which would be called upon successful processing at MTS

Callback HTTP Method

HTTP Method (POST/PUT/GET/PATCH) used while MTS makes the callback

Callback Timeout

Timeout awaited by the callback until acknowledged with a response.

Callback Auth Type

Type of authentication expected by callback URL. MTS-C currently support Odoo type which uses the session-based authentication implemented by Odoo.

Callback Auth Database

DB instance used by Odoo.

Callback auth username

Username to access callback API

Callback auth password

Password to access callback API

Output format is a string which will be used by MTS to format its output to suite the caller's requirement.

A can be used to identify the records for tokenisation. For. eg. Only records which have VID associated with it and are not tokenised need to be picked for tokenisation.

🔗
MOSIP Auth Token
MOSIP Token Seeder
MTS
JQ
domain filter