OpenG2P can use e-Signet for authentication. e-Signet provides an OIDC interface for authentication while connecting to the MOSIP's IDA services on the backend.
Here, OpenG2P is a Relying Party and the Authentication System is MOSIP. Learn more.
Refer to the guide Integrate MOSIP e-Signet.
OpenG2P integrates with MOSIP to verify the UIN/VIDs provided by individuals as part of the registration process. As a result of the verification, OpenG2P receives a unique token against an individual's UIN/VID along with KYC data. This data is stored in the registry.
There are two ways to obtain the MOSIP tokens:
For new registrations that are conducted via ODK form, The MTS Connector is configured to pull data directly from ODK Central and return MOSIP tokens. See ODK MTS Connector.
For already existing records in the registry, the Registry MTS Connector is used to trigger a connection with MTS and in turn receive MOSIP tokens for all the records requested.
ODK MTS Connector is an OpenG2P Odoo addon that fetches tokenised data from the ODK Central by calling the (MTS) and stores it in the registry.
Uses callback delivery type of MTS
Completely asynchronous execution
OpenG2P can schedule a daily job to fetch the delta for the day
Manual import feature (TBD)
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.
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
| Property | Configuration |
|---|
| Property | Description |
|---|---|
Name
A string to identify the connector
URL to reach MTS
URL for MTS API
MTS Input type
MTS-C connects over "ODK" which is the first option in this selection. OMC option could be proceeded by selecting OpenG2P Registry.
Mapping
MTS Field mapping as required by the API. Refer to MTS Documentation. The format of Mapping would be JSON.
Output Type
MTS-C only supports JSON output type of MTS.
Output Format
Output format is a JQstring which will be used by MTS to format its output to suite the caller's requirement.
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 provides both recurring and one time execution. Recurring can be configured to do continuous pull from the ODK over MTS.
Interval in minutes
Interval at which the MTS-C job runs.
MOSIP Language
MOSIP language setup. The default is "eng".
ODK Base URL
Base URL or the complete domain address for the ODK central installation
ODK Odata URL
OData service (.svc) URL for the ODK form to fetch the submissions.
ODK User email
Email Id to authenticate MTS for accessing Odata URL
ODK User password
Password used to authenticate Odata URL
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
| A string to identify the connector |
| URL for MTS API |
| OMC option could be proceeded by selecting OpenG2P Registry. |
| MTS Field mapping as required by the API. Please refer to MTS Documentation. Format of Mapping would be JSON. |
| MTS-C only supports JSON output type of MTS. |
|
| 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. |
| MTS-C provide both recurring and one time execution. Recurring can be configured to do continuous pull from the ODK over MTS. |
| Mosip language setup. Default is eng. |
| Interval at which the MTS-C job runs. |
|
| 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. |
| A URL endpoint which would be called upon successful processing at MTS |
| HTTP Method (POST/PUT/GET/PATCH) used while MTS makes the callback |
| Timeout awaited by the callback until acknowledged with a response. |
| Type of authentication expected by callback URL. MTS-C currently support Odoo type which uses the session-based authentication implemented by Odoo. |
| DB instance used by Odoo. |
| Username to access callback API |
| 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.
