Operational Considerations

This section covers following requirements needed to run the MOSIP–CRVS integration.

Use it to create the operational entities that CRVS-initiated workflows depend on (centres, machines, officers, and an application identity).

• Create Centre: Create a centre to represent the physical/organizational location where CRVS operations are anchored.

• Create the Default Officer: Configure a default officer for cases where the system needs an operational “owner” for a transaction.

• Create Machine: Register a machine/device that will be associated with a centre for operational tracking and access controls.

• Map Officer to Centre and Machine: Assign an officer/operator to the right centre and machine so transactions are authorized and auditable.

• Create the Application ID (AID): Create an application identity used by CRVS-initiated flows and integrations where an AID is required.

---

Learn more

• Security & Authentication - OAuth client setup, access tokens, and eSignet flow.

• Policy Configuration & Customization - Credential sharing choices (PSUT/UIN/VID) and partner policy setup.

• Notifications & Event Handling - WebSub topics for credentials and packet status updates.

• API Reference & Data Models - Packet APIs, payloads, and data structures used by CRVS.

• Core Integration Principles - Trust boundary, verification expectations, and defaults.

• MOSIP Configuration Changes for CRVS Birth and Death Requests - ID schema fields, auth-policy updates, and routing configs.

• Error Handling & Reconciliation - Failures, retries, and reconciliation patterns.