Rework confirm registration endpoint to support upcoming integrations

[euanmillar]

MOSIP - Open Source Identity Platform

🔁 Current state

Currently the country config event-registration handler calls workflow -package to add the necessary identifiers for a child (a national id / NIN for example). We can implement MOSIP integration here, waiting for the MOSIP to respond and then calling the CONFIRM_REGISTRATION_URL.

When a person dies, core has hardcoded ways of passing information to MOSIP.

Problems with the approach

• Security: instead of calling workflow directly via CONFIRM_REGISTRATION_URL, it needs to go via gateway-service to allow one entrypoint only to core
• Error handling: we need a new rejectRegistration endpoint if MOSIP cannot register a NID
• Country-config upgrading ease: country-config needs to have less code to make upgrades easier
• Core separation of concerns: core now has code and references hardcoded to MOSIP - we want core to be integration-agnostic

🚀 Proposal

High-level diagram of the proposed flow

In short; the country config event-registration handler (which calls reject or confirm) should be able to be commented out and 'hijacked' by an integration like MOSIP.

• Allow an HTTP request with a correct token to confirm or reject the registration via gateway
• Import event-registration -route from MOSIP repository. This route calls the OpenCRVS-side MOSIP-mediator