Need more explanation on identity-mapping.json and id-authentication-mapping.json

Support
,
1

Hello there,
I am setting up a custom ID Schema for my MOSIP Installation and I need some more explanation on how to correctly edit these mapping files.

(1): is the key name fixed? I guess I can’t change it?
For example: can "addressLine1":{"value":"addressLine1"} be changed to "addressLineAll":{"value":"addressLineAll"}

(2): my ID schema does not have addressLine2 and addressLine3 so what can I do in this case?

2

Dear @smraa

Welcome to the MOSIP Community, and thank you for your query.

Yes, you are absolutely right you can rename the key like:

"addressLine1": { "value": "addressLine1" }
to something like
"addressLineAll": { "value": "addressLineAll" }

This is valid as long as you update all the corresponding references accordingly in:

  • Identity Mapping JSON
  • UI Specifications (both Pre-Registration and Registration Client)

For the second question:
If your ID Schema doesn’t include addressLine2 or addressLine3, you can:

  • Remove them entirely from the mapping JSON files (if not needed),
  • Or mark them as non-mandatory in the schema so they can be skipped during data collection.

However, please make sure the following dependencies are always synchronized whenever you make changes to the default ID Schema:
Dependencies to update:

  1. UI Specifications
    • Pre-Registration
    • Registration Client
  2. Identity Mapping JSON (used by Pre-registration Back Office & Registration Client)
  3. ID Authentication Mapping JSON (used by IDA for e-KYC / Auth)
  4. Applicanttype MVEL (used for validation in the Registration Client)

You can refer the Reference:

Please let us know in case you need any help.

Best regards,
Team MOSIP

1 Like
3

Thank you. I will try this.

1 Like