Page Comparison

Current issues and challenges

• The current focus is on getting the deployment issues sorted out for deployed a minimum set of BB components for MOSIP and MIFOS on BB components in the Sandbox for the MVP Happy Flow implementation.

  • However, it is also important to consider how we will we test the functionality of the BB implementations once it is deployed in the Sandbox.

  • Currently, the API test harness is outside the Sandbox and is used to qualify the compliance of the BB implementations against BB specifications.

  • Once the BB implementations are deployed in the Sandbox, we will need to do the functional testing too. This aspect needs to be thought through.

• The deployment of a minimal setup of MOSIP in Sandbox is posing challenges as it is not possible to deploy MOSIP in a single container with only the minimum set of components. More on this and resolution provided by Technoforte is provided below.

Deployment of MOSIP Mock ID implementation for MVP

• To address the MOSIP deployment challenges, Technoforte suggested using the mock ID system

  • This will have the e-Signet module in place with some minimal dependencies.

  • However, it will not have all the MOSIP modules, but only have the demographic details and some foundational ID’s created against it.

  • If that is ok for the MVP, we can consider deploying the Mock ID for the MVP Happy Flow.

  • Since there is no specific client requirement for the MVP, it is ok to use the Mock ID provided it can be easily replaced by the MOSIP DPG without a lot of rework and effort.

  • The key issue is not about doing some kind of a mock implementation here, it's about trying to be as close to the final USCT implementation as possible. So, if it is extremely challenging to only deploy a few modules of MOSIP for the happy flow path, then perhaps we are not left with any alternative but use the mock ID.

  • The Mock ID system will not have the MOSIP ID generation process which involves ID registration, repo, etc. Rather it will just have the e-Signet which the MVP can use for authentication. So, in this case we will be able to authenticate only with the demographics and OTP authentication but not biometric authentication.

  • Even though we may decide not to have biometric authentication in this iteration of the MVP, we should in future after this iteration scale it to other modes of authentication. It is important to have that in the road map. Otherwise, it will not be tested when there is an actual customer, we will still not know how to include those features. Hence, there is a need to slowly grow the capabilities of the USCT demos in the sandbox as we separate them out in terms of now and future iterations, but we should not miss them in this process.

  • The Mock ID system is plug-and-play in the sense that the e-Signet application can be integrated with it for the MVP and later that can replaced with the actual MOSIP DPG. The Mock ID will also be compliant with the GovStack ID BB APIs

  • Based on deployment experience of MIFOS, the Sandbox team estimates that though the Mock ID is a scaled down version of MOSIP, the deployment time and effort is certainly not trivial and cannot be done in just a few days.

  • The agreement is that Sandbox will work on deploying the Mock ID based on the information to be provided by Technoforte, so that the deployment is not held up while they are also parallely mapping the API endpoints required for the MVP Happy Flow.