Technoforte-MOSIP-GovStack Discussion @ Bangalore - 27-06-2023
Please find the minutes of the meeting held on 27-06-2023
Attendees:
Yogesh
SasiKumar
Vishwa
Sagar
Hareesh
Jane
Smita
Agenda:
Handover from Sasi for Enrollment API
Clarify security concerns about Enrollment API
Finalize the MOSIP API as the baseline for the Enrollment API
Discussion points:
An authorized entity must call the Enrollment API over a secure interface.
Use cases discussed:
Demographic database, but no biometric database: Data goes to pre-registration and the biometrics are captured
Democratic database and biometric database: Port demographic data and biometric data
No demographic or biometric database: Follow a MOSIP-like registration approach
Capturing Biometrics is optional
MOSIP schema is proposed, though CRVS can also use their own schema.
MOSIP Packet Manager createPacket API will be used as baseline for Enrollment API:
Audit details are very useful information for centre operators. However, this is optional for GovStack
AdditionalInfoReqId is not required and will have an empty/Null value
metaInfo captures operator details, machine Id, etc. and will be optional
Currently, the createPacket API doesn’t trigger the packet processing. A wrapper API should be implemented to start the packet processing
The CRVS can use their own implementation if don’t wish to use MOSIP RegClient as long as the interface is secure, use HTTPS, and is operated by authorised entities
SBI must be used for biometrics
Enrollment API is not open for all the web browsers to implement and the interfaces calling this API have to be authorized.
These meeting minutes were also captured in a recording. This is the recording link: https://technofortespl-my.sharepoint.com/personal/hareesh_g_technoforte_co_in/_layouts/15/stream.aspx?id=%2Fpersonal%2Fhareesh%5Fg%5Ftechnoforte%5Fco%5Fin%2FDocuments%2FRecordings%2FEnrollment%20API%20discussion%2D20230627%5F141816%2DMeeting%20Recording%2Emp4&ga=1
A presentation was also prepared to collate these points in the pdf.