Release Version: 1.2.1.0-beta.1

Release Type: Beta Release

Release Date: Coming Soon

Overview

This component wise beta release introduces significant enhancements, including migration to Java 21 for improved compatibility and performance, the categorization of MOSIP data into default and seed data for streamlined deployment and customization, and support for new cryptographic algorithms (SECP256K1, SECP256R1, and Ed25519) to strengthen security

Additionally, transitioning from the landing zone folder to the MinIO object store addresses scalability and storage challenges, ensuring efficient data handling.

This release has been tested with and supports eSignet 1.3.0. For users who have already deployed MOSIP and intend to upgrade to Java 21, please refer to this guide (link to be updated soon) for a detailed step-by-step process to ensure a seamless transition.

As part of the Java 21 migration in this beta release, users must follow specific steps to migrate Artifactory and MOSIP configuration files. Before proceeding with the migration, ensure that two separate Artifactory servers are running:

1. Java 11 Artifactory Server: This is for repositories not yet compatible with Java 21 in this beta release.

2. Java 21 Artifactory Server: For repositories that support Java 21.

This setup ensures compatibility and seamless operation of Java 11 and Java 21-supported repositories. Any latest Java 11-compatible Artifactory server can be used for this purpose.

Major Areas of Work

• Code Migration from JAVA 11 to JAVA 21

• Enabling Digital Signature with ECC Algorithm in Key Manager

• Data Segregation to Default, Seed, and Test

• Functional bug fixes

• Security bug fixes

• DSL Automation

Repository Released

Documents for reference

• For module wise Enhancements & Bug fixes please refer here.

• Functional test report (To be updated).

• For Known issues, please refer here.

Enhancements

1. Data Segregation (MOSIP-26804): MOSIP data which was considered to be master data have been categorized into default data and seed data. Default data refers to data that are mandatory to proceed with the deployment of MOSIP. Seed data refers to the data that are not mandatory during the deployment but are required for the functionality. this data will be fed by the countries based on their requirement. In this release, the categorization of the data performed and CSV files related to default data have been placed along with the source code while the CSV files that are related to seed data have been moved to the mosip-data repo. As part of this process, data that are not required anymore also have been removed. Please refer to the below changes:

• Few language specific data which was identified as default data have been moved to the admin repo also modified these tables to be language agnostic. Below is the list of changes made under this category:

app_details
authentication_method
biometric_attribute
biometric_type
module_details
process_list
reason_category

• The below tables which are placed under admin_service were deleted as they are not in use anymore in LTS- - 1.2.x

master-admin_param.sql
master-appl_form_type.sql
master-message_list.sql
master-doc_format.sql
master-gender.sql
master-global_param.sql
master-id_type.sql
master-individual_type.sql
master-introducer_type.sql
master-status_list.sql
master-status_type.sql

• The below tables were identified as seed data and hence moved to DML in mosip-data.

days_of_week_list
doc_category
registration_center
registration_center_h
template
template_type
reason_category

• Removed DML data from mosip_data as it is present already in the admin repository as default data.

app_authentication_method
app_details
app_role_priorityy
authentication_method
biometric_attribute
biometric_type
process_list
module_details
role_details
screen_authorization
screen_details
template_file_format
blacklisted_words
sync_job_def

To modify all the tables as mentioned above the user needs to execute the SQL script given here.

1. Support for SECP256K1, SECP256R1, and Ed25519 Cryptographic Algorithms(MOSIP-33780): The system is enhanced to support additional cryptographic algorithms based on Elliptic Curve Cryptography (ECC), specifically SECP256K1, SECP256R1, and Ed25519. These algorithms were integrated into the key management system to enable secure key generation, signing, and verification functionalities. Please refer here for more details

2. Codebase Enhancements with Java 21 for released repos(MOSIP-21117): This release introduces extensive enhancements to align the codebase with the latest features, optimizations, and requirements of Java 21. These updates ensure seamless compatibility, improved functionality, and optimized performance with the new Java version. As a part of Java migration, the Spring boot version also got updated. Here on, the platform will support the Spring boot v3.2.3.

Refer to the below repositories that are released with JAVA 21

• admin-services

• audit-manager

• otp manager

• print

• websub

• biosdk-client

• biosdk-services

• nfiq

• mosip-config

• registration

• mosip-openid-bridge

• captcha

• digital-card-service

• admin-ui

• packet-manager

• reg-client

• mosip-ref-impl

1. Standalone Data Share Service(MOSIP-34253): enhanced the system's ability to run the data share as a standalone service, eliminating the dependency on the Partner Management Service and Key Manager Service. In this mode, the data share process is simplified: INJI will trigger the Durian service with a profile configured for standalone mode. When enabled, static values for policyid, subscriberid, and transactions allowed will be picked from a configuration file. Durian will then generate a datashareURL based on these static values, which will be shared with INJI for further use. This enhancement ensures that data sharing can proceed independently of the default setup, streamlining the process for specific use cases. The data is stored as plain text, with a unique resource location per VC, ensuring persistence without automatic purging. This feature is to support the request from Inji Stack only

2. Code Enhancement:

   • Updates in Artifactory and MOSIP Configuration

     As we are aiming to streamline dependencies, optimize configuration management, and improve system functionality, several updates have been made to the Artifactory and MOSIP configurations. Key changes include:

   • HSM Client Updates: The HSM client file in Artifactory has been updated to support Java 21.

   • Kernel Transliteration Dependency: The kernel-transliteration dependency has been moved to the pom.xml file to centralize commonly used files within a centralized repository.

   • New JAR Files Added:

     • registration-api-stub-impl.jar

     • image-compressor-jar-with-dependencies.jar

     • redis-cache-provider.jar

   • ChildAuthFilter Refactor: The childAuthFilter JAR file has been removed from Artifacory. Related code snippets have been moved to ID Repo to eliminate Artifactory dependency in the ID Repo module.

   • Multilingual Support: To enhance multilingual capabilities and support data segregation, the i18n bundle has been introduced for Admin, PMS, and Pre-registration modules.

     • The attribute `config.server.file.storage.uri` has been renamed as below:

     mosip.config.server.file.storage.uri=${spring.cloud.config.uri}/${spring.application.name}/${spring.profiles.active}/${spring.cloud.config.label}/ delta

     • As part of Spring-boot 3.x migration property server.max-http-header-size is deprecated and the below property is used: server.max-http-request-header-size=${server.max-http-header-size}

   • The below property which is used to define vc verification file urls has been moved from id-repo to application-default property files: mosip.vercred.context.url.map={"https://www.w3.org/ns/odrl.jsonld" : "odrl.jsonld", "https://www.w3.org/2018/credentials/v1" : "cred-v1.jsonld", "https://${mosip.api.public.host}/.well-known/mosip-context.json" : "mosip-context.json"}

   • A new property: registrationcenter.centerdetail.rest.uri=${mosip.base.url}/v1/masterdata/registrationcentershas been included in the pre-registration-default.properties` file which will be used to retrieve center details during the appointment booking process

   • Property related to the Maximum age limit has been removed in the config file ‘registration-default.properties’.

Bug Fixes

In addition to the bugs mentioned above, several other issues have also been resolved. For detailed information, please refer to this link.