Version: 1.1.5

• Name: Interim Release

• Date: April 23, 2021

• Recommended Patch for 1.1.5: 1.1.5.5

• Support Sunset Date: June 2022

• Recommended Upgrade Version: 1.2.0.1

• Release Notes

Version: 1.1.4

• Name: Interim Release

• Date: February 12, 2021

• Recommended Upgrade Version: 1.1.4.6

• Release Notes

Version: 1.1.3

• Name: Interim Release

• Date: December 14, 2020

• Release Notes

Version: 1.1.2

• Name: Interim Release

• Date: October 24, 2020

• Release Notes

Version: 1.1.1

• Name: Patch Release

• Date: September 14, 2020

• Release Notes

Version: 1.1.0

• Name: Real Biometrics

• Date: July 03, 2020

• Release Notes

Version: 1.0.6

• Name: Real Biometrics

• Date: February 11, 2020

• Release Notes

Version: 1.0.5

• Name: Real Biometrics

• Date: January 08, 2020

• Release Notes

Version: 1.0.0

• Name: Real Biometrics

• Date: December 06, 2019

• Release Notes

Version: 0.9.0

• Name: Proxy Biometrics

• Date: July 01, 2019

• Release Notes

This document contains the features that were developed or enhanced as part of MOSIP 1.1.5 release.

Commons

• Web Sub Upgrade

  • WebSub messages are now being persisted in database.

  • Web sub notifications are handled after the restarts, so that, the subscriber should continue to receive the messages even after restarts.

• New script are created to handle the deployment of master dml data that convert the excel file to CSV format on the fly and upload the data.

• JCE (Java Cryptography Extension) integration in keymanager service is done in order for HSM to work with the FIPS 140-2 mode and also implement standard encryption algorithm and key generation.

• Track of all the audit trails for events executed in various modules in MOSIP.

ID Authentication

• We are now sending certificate thumbprint in e-kyc response for handling key rotation.

• We are now handled the failed request in credential modules with a new API to retrigger a failed record.

• The biometric extractor service is now removed, and the logic for bio-extraction for different formats and different SDK HTTP URLs is merged into ID repository identity service.

• We have now implemented retry mechanism for credential store with batch job when there is an error occurring in retrieving/storing credential data.

• We have now included retry logic in REST API calls and keymanager encryption/decryption in IDA and ID Repository.

• We are now capturing authentication transaction history for authentication transactions with validation failures (example - invalid UIN or VID).

Partner Management

• We have now introduced a new search API in partner management system for fields such as policy, policy group, partner, partner type etc.

• We have now merged all partner services by having separate grouping of poilcy related and partner related micro service.

• We have updated the policy approval flow to enabale auto approval mechanism for subsequent API key request from same partner.

• We have depricated the device register and deregister APIs as from now onwards we would be performing trust validation.

Resident Service

• We are now able to identify and send the best two fingers to print partner.

• We have added certificate thumbprint in resident service as part of authentication API request and send it to ID Authentication.

• The Resident services now has a new generate OTP API instead of generating OTP via ID Authentication OTP request API.

Registration Processor

• We have now included expiry in vertx and kafka event bus messages.

• We have now included Packet tagging based on specific criteria such as age group, gender, resident type, biometrics exception scenarios and also route the packets to various workflows based on tags.

• We have moved away from one minio bucket for each packet to single bucket for all packets in minio and have one folder and corresponding files for each RID (this is a performance fix for Registration Processor).

• We have now replaced the spring cache type with the hazelcast in-memory caching mechanism provided by the spring boot.

• We now have expiry time configured for any message sent in for ABIS queue and manual adjudication queue. Once the message has exceeded the expiry time then the packet is marked for reprocessing.

• Packet manager in registration processor is now able to retrieve the data based on the priority set in a policy defined by the stage.

• Upgraded manual verification stage in MOSIP to take a decision based on the results from manual verification system (reject or process the packet).

Registration Client

• We have now enabled forgot password and reset password functionality in registration client through integrated IAM.

• We now store only operator's biometrics templates or extracts in registration client (not the images) for local authentication after onboarding of the operators.

• We now support regex validations for primary and secondary languages for simple type attributes.

• We now perform JWT verification of header and signature before accepting the payload data from MDS.

• Registration client now performs the trust validation of the devices by verifying whether the digital id block and the data block are actually signed by a MOSIP verified device provider. Hence, storing device details in master database or device registration is not requiered for device validation.

• Tracing of requests and event messages in registration processor stages with all logs in place.

• We now handle deactivation or activation scenarios in registration client for user, machine and center.

Pre Registration

• We have added a proxy layer between the pre-registration UI and master data API. All the calls are happening via. the pre-registration service.

• We have removed keycloak integration for storing pre-registration user sessions. Pre-registration sessions are now created in pre-registration database.

• Pre-registration now has its own OTP transaction table & service to perform OTP authentication.

• Encryption of pre-registration data before storing in database was done using the root key for registaration (ApplicationID=REGISTRATION, ReferenceID=""), now the encryption is performed using the keys generated from pre-registration root key (ApplicationID=PRE_REGISTRATION, ReferenceID=INDIVIDUAL).

• Support for encryption using preprend thumbprint has been added.

• Gender and resident status attributes are now treated as dynamic fields in pre-registration.

• We have added pagination option in the UI and API for list of registration centers.

• We have now added new control types such as buttons to the UI specification.

• We are now able to make the field required or not by giving required condition in UI spec.

• Support for document number has been added during document capture.

• Pre-registration UI specification now supports multiple location hierarchy for present address, temporary address or place of birth.

• We are now handling applicant type field dynamically using mvel expression.

• We have now added visibility condition in pre reg UI spec for showing or hiding the UI fields.

Biometrics

• Reporting mechanism has been incorporated into SDK test kit

This document contains the defect fixes and features that were released as part of various patch versions on top of MOSIP v1.1.5 release.

MOSIP v1.1.5.1

Bux fixes and features released

Registration Client

• Fix for removal of user role not getting reflected in registration client has been provided

• A new datatype called “date” has been added in the registration client UI specification

• Fix for issues in multi-lingual drop downs due to visibility has been provided

• The flag for skipping trust validation has been removed from the registration client

Partner Management

• Fix for MOSIP signed certificate to be updated in the master.ca_cert_store table instead of the CA-signed certificate has been provided.

Commons

• Issues related to the thumbprint has been resolved. The key manager will handle both scenarios where a thumbprint is passed or not passed for decryption.

ID Authentication

• Now in demographic authentication & e-KYC, all the demographic attributes in id schema can be passed (if available in the id-authentication database).

• Integration with the latest key manager done, this had the thumbprint fix.

MOSIP v1.1.5.2

Bux fixes and features released

Across Modules

• The jaxb-api library dependency was updated for most of the repositories.

Admin Services

• The sync API has been modified for making sure that all the certificates are getting uploaded to the registration client certificate trust store.

MOSIP v1.1.5.3

Bux fixes and features released

Commons

• Fix has been provided for packet priority based fetch when there is more than one packet. Earlier we had observed that if there is more than one packet being used then correct data was not sent.

• Fix has been provided so that certificates can get downloaded and stored in the registration client trust validation irrespective of timezone difference in server and client.

ID Authentication

• Photo is now being sent in e-KYC response

Registration Client

• Fix for the registration client not able to detect the devices when started before the SBI has been provided

• Fix has been provided to stay on the acknowledgement page after printing so that the user can reprint the acknowledgement. Earlier after the print button was clicked the user was automatically redirected to the home screen hence reprinting was not possible.

• The issue in age calculation in the registration client due to different windows region formats has been fixed

MOSIP V1.1.5.4

Bux fixes and features released

ID Authentication

• Due to recent MDS specification changes we have modified the below sections in IDA.

  • Thumbprint in IDA now supports both hex and base64URL encoding

  • Hash validation for biometrics has changed with an option to disable it

Registration Client

• Document Scanner

  • Fix for creation of low-resolution image due to cropping has been resolved

  • Zoom in and zoom out feature has been added in preview in document screen

  • Document Scanner screen now has a horizontal and vertical scroll

  • An option to change the crop area by dragging after crop selection has been added

  • JPEG compression is done on the scanned or cropped image before converting it into a PDF, which decreases the document size

• Biometric Capture Screen

  • Post capture of Iris and Face we are now showing the captured biometric image in the UI (not the last frame)

  • Display issue related to good quality image replacing a lower-quality image during multiple capture attempts in biometric capture screen has been fixed

  • Display issue related to the warning symbol not getting removed after a proper capture has been resolved

  • The forced capture limit is now, same as the capture limit (it was earlier hardcoded to three)

Registration Processor

• Adjudication Stage

  • The stage can now handle multiple technical failures and redirects them for reprocessing. Scenarios,

    • Any technical failures sent by the adjudication system (when return code is sent as 2)

    • When an invalid reference ID is sent from the adjudication system

    • When there is a count mismatch between the count value and reference IDs

  • The stage also handles a scenario where multiple responses are received from the adjudication system, by just logging the response and not processing it

  • The adjudication response now supports the modalities section for each reference ID

• Readiness Probe for registration processor stages

  • The readiness probe details in all registration processor VertX stages have been modified to remove the null pointer exception during the restart of the VertX stages

  • Prometheus endpoints have been added for all the stages

• Option to have multiple landing zone folders has been added

• Issues in stage level packet priority-based fetch for biometrics has been fixed for uin-generator-stage

• Issues related to packet validation failure to reprocessing of multi-source packets has been fixed

Commons

• Packet manager has been modified to fetch proper biometric data during reprocessing of multiple packets

• A flag has been added for the UIN validator for disabling the validation for “repeating numbers for 2 or more than 2 digits”. Due to this change dependency in the below modules has been updated.

  • registration-client: 1.1.5.4

  • id-authentication: 1.1.5.4

  • id-repository: 1.1.5.3

  • resident-services: 1.1.5.1

ID Repository

• Aspect logs have been added

• The column bio_ref_id in the idrepo.uin table has been deprecated

This document contains the features that were developed or enhanced as part of MOSIP 1.1.4 release.

Overall Enhancement

• Prepend thumbprint has been added for all the modules where encryption or decryption is used in MOSIP and it is made configurable to make it backward compatible.

Commons

• Datashare has been upgraded

  • Kernel Auth adapter JAR dependencies are removed.

  • The JWT signature header is now stored as metadata in object store when a data share URL is created.

  • The signature from metadata is added in the response header for get API.

  • Prepend thumbprint support for encryption has been added.

• Kernel ID Generator Service for VID has been modified

  • Assigned VIDs are isolated to a separate table to improve performance.

  • Expired VIDs after the cooling period are deleted instead of adding back to available VID pool to make available VIDs truly random.

ID Authentication

• Signature verification of the authentication request and biometric data with trust validation has been added.

• Decryption of authentication request and biometric data with certificate thumbprint has been added.

• We are now using HMAC Utils 2

• Authentication Transaction history is now storing the request and response signatures

• The Auth Demo UI has been updated to support,

  • Signature in header.

  • Authentication request and biometric data with certificate thumbprint.

  • Use of HMAC Utils 2.

• Ability to receive web sub notification & update IDA cache has been added for any change in policy or partner details in partner management module.

• Root and CA certificates of the partners are stored now stored in IDA database for trust validation.

ID Repository

• Credential Service Upgrade

  • We are now fetching the policy details based on issuer details and credential type, previously we used the hard code the policy id.

  • We are now using the new key manager service for encryption with prepend thumbprint.

• ID Object Validator Upgrade

  • The ID object validator now supports master data validation for the dynamic location hierarchy, previously it used to perform validation for the static fields defined in the platform location hierarchy.

• Added certificate thumbprint support for encryption or decryption of data.

Partner Management

• The validate partner API when called by IDA now returns the partner certificates in response so that it can be used during encryption for e-KYC response.

• We are now sending web sub notification for IDA when there is a change in policy, partner and API key details.

• We have added multiple APIs in Partner Management for Partner Management UI Screens.

Registration Processor

• We are now using the get certificate API in registration processor to retrieve the IDA certificate for encryption instead of using the get public key API.

• We are now using Kafka queue as configurable replacement for vertx event bus in registration processor for providing delivery guarantee of all messages in the queue. The approach taken here makes the event bus usage a proper factory implementation and includes vertx and kafka as one implementation.

• Vertx version in stages has been upgraded to 3.9.1 from 3.5.4 to utilize new capabilities.

Registration Client

• Feature to hide and show fields has been added using rules in Registration Client UI Specification.

• Support for Logo display in preview and acknowledgement page has been added.

• Document scan pop-up now supports stream, preview, crop and cancel options.

• User details sync in now integrated with the new sync data API; this API (/userdetails?keyindex=<keyindex>) now returns encrypted user details.

• Operator details are now added in the EOD action page.

• We are now display date & time in local timezone where the registration client is running.

• Support for document number has been added during document capture.

This document contains the features that were developed or enhanced as part of MOSIP 1.1.2 release.

Commons

• Kernel Log Manager has been modified.

  • Logging framework has been changed from log4j to logback.

  • Spring Sleuth has been integrated in Kernel Log Manager.

• Data Share Module has been added to share data inform of sharable URLs to external entities.

• Packet Manager has been modified to support creating and reading packets as per our new packet structure.

• Multiple adapters (Posix, S3 & Swift) have been added to connect with Object Stores.

• The passwords in configuration data is now encrypted and stored.

• APIs to add Certificate Authority & Sub-Certificate Authority has been added.

• Kernel Key Manager has been modified.

  • Key Manager related tables have been moved to a new database.

  • Support for Offline encryption & decryption has been added for encryption in Registration Client.

  • Support for PIN based encryption and decryption has been added.

• Integration with multiple Real HSMs was done.

• Web Sub has been added to integrate with external componets like Print & Postal service providers.

• Open ID Adapter was developed, so that MOSIP would be able to connect with any IAM provider.

• Commons repository re-structuring has been done to merge common components.

Administration

• Feature to upload exported packets from Registration Client has been added.

• Feature to bulk insert, upload or delete - master data using csvs has been added.

• The APIs for Devices, Machines and Users have been modified to support mapping & unmapping of Registration Centers.

• The database for master data has been modified.

  • Unwanted tables have been reviewed to removed.

  • Mapping tables have been removed & one-to-one mappings have been added to respective tables.

  • Device Regitration tables have been moved to new database.

Pre-registration

• Services in Pre-registration are re-organized to merge common services together.

• Documents are now being stored in Object Store using our new Object Store adapters.

• UI has been modified to resolve usability issues.

  • Support to capture age and date of birth has been added.

  • Calender has been removed for date of birth capture, instead text fields for capturing Date, Month & Year has been added.

Registration Client

• Packet creation is now being performed using the new Packet Manager.

• UI has been modified to resolve usability issues.

  • Back button has been added in login screen to update the username.

  • Biometric capture screens have been updated.

  • UI has been resposive for Single & Multi-language.

  • Templates in Registration Client have been modified.

• Export to Device feature is now available to export packets to external hard drive.

• Direct call to notification service has been removed. Now, notification for registration would be sent to resident when packet reaches the server.

• Sync data is now being encrypted using TPM.

• Implementation for Proxy MDS has been removed.

Registration Processor

• Implementation in Registration Processor has been made to read packets using the new Packet Manager.

• Packets are now being stored in Object Store using the object store adapter.

• Biometrics are now being shared to ABIS using a data share URL.

• Data is being sent to Manual Adjudicator using data share URLs.

ID Repository

• ID Repository has been moved from commons to a new repository.

• Extraction module has been added to extract biometrics into templates using biometric extract SDKs.

• Credential Issuance module has been added to share credentials based on policy.

Authentication

• Authentication Transaction has been modified to store tokens instead of storing encrypted UIN or VID.

• Implementation has been made to support capture of consent token in header for authentication request.

• Authentication token generation is now driven by authentication policy for the partner.

• Locking/unlocking of authentication for an individual has been moved to ID Repository.

• Integration with Web Sub was done to receive ID details from ID Repository.

Partner Management

• Partner Management APIs have been created, to support,

  • Self-registration of various types of partners (like, device providers, FTM providers, authentication partners, credential partners, etc.)

  • Device & FTM Make-Model registration.

  • Secure Biometric Interface registration.

  • Approvals of the above by the Partner administrator.

• Policy Management has been modified to support authentication as well as data share policies.

Resident Services

• Demographic update implementation has been updated to create update packet using the new Packet Manager.

• Credential Issuance has been added using ID Repository's credential issuance module.

• API for verifying the credential issuance and print request status has been added.

This document contains the features that were developed or enhanced as part of MOSIP 1.1.3 release.

Commons

• Key Manager is now enhanced with the below features,

  • Key Manager now supports encryption and decryption of registration packets using the thumb-print.

  • JWT Sign and JWT Verify APIs have been introduced to support full JWT signature validation with proper header and additional parameters.

  • An API has been added to validate certificate trust path for a certificate and partner domain.

  • We have removed the get public key API, which was used to fetch the public key. We recommend to use our get certificate API to fetch MOSIP’s public certificate.

• Data Share is now enhanced with the below features,

  • The expiry for the data share URL has been added. The data share URL will not be accessible if the expiry time for the URL has exceeded.

  • As the data share policy structure has been changes in partner management, subsequent changes have been incorporated in data share.

Pre-registration

• Mandatory field labels in Pre-registration UI are now dynamically appended with a red asterisk symbol (*).

Registration Client

• Direct call to internal authentication API during operator on-boarding has been removed from registration client. This call is now being routed via. Registration Processor.

• Issue with Biometric Stream API (for 0.9.2 MDS) has been fixed - Hence, Registration Client is compatible with MDS 0.9.2 and 0.9.5 specifications.

• User Salt sync has been removed from Registration Client syncs. Now, the salt is being generated on the fly in Registration Client, its not being fetched from the server.

• The client settings (master data) and configurations are now encrypted using the TPM public certificate of the Registration Client and synced.

• Registration Client UI Specification is enhanced with the below features,

  • Support for alignment has been added

  • Support for multiple location hierarchy in case of present and permanent address has been added

Registration Processor

• APIs have been created in Registration Processor, to delegate the internal authentication request and fetch encryption certificate calls from Registration Client to IDA.

• Print Service has been deprecated from Registration Processor. A new project has been created for Print Service.

• Print Stage in Registration Processor now calls the credential request generator to send print requests via. web sub.

• In our earlier releases all the data captured during registration was sent to ABIS systems, but now, we are reading the policy and sending specific biometrics to the ABIS Partners. This has been bought in after the changes in our data share policy changes in partner management.

• Source and Process details are now added in the registration processor ID mapper, so that the Registration Processor stages can make a call to the packet manager based on the values mentioned in the ID mapper.

ID Repository

• As part of the credential issuance, we are now sending an additional information to the partner stating which attributes are encrypted and which are not.

• The credentials sent to the new print service will now be encrypted using print partner’s encryption certificate.

• During e-UIN card request, if the user makes a request using a particular VID then the same VID would be sent to the Print Partner.

• As part of credential issuance, MOSIP credential service will share data with partners (IDA Instances or Print Partners) on web sub as per our standard schema. A sample schema would be published so that the partners can easily integrate with MOSIP.

• The entire credential details shared to partners in the web sub response will be encrypted using the partner encryption certificate.

• As the data share policy structure has been changes in partner management, subsequent changes have been incorporated in credential issuance.

ID Authentication

• Data fetched from Partner management (partner and policy details) and stored in IDA using Spring Cache.

• All the IDA APIs are modified to remove ID Type from them. We would be using the ID value to identify if the input id is a VID or UIN.

• Notification templates and titles were earlier part of IDA configurations. Now they are fetched from master data and stored in IDA using spring cache.

Partner Management

• APIs have been created to add or retrieve biometric extractor details based on policy.

• The policies (authentication and data share policies) are now generated as per our new policy schema.

Resident Services

• As the IDA APIs are now modified to remove ID Type from them, the APIs in Resident Services are also modified to remove ID Type from them.

• For features such as request for e-UIN card and QR code the new print service implementation is now being called via credential issuance web sub to generate the e-UIN card and QR code (verifiable credentials).

Administration

• Key Management UI has been added in Administration Portal.

Print Service

• A new implementation has been created to receive requests to generate e-UIN card or QR codes using input received from Credential Issuance via. Web Sub.

Table Of Contents

• Scope

• Documentation

• Code

• Tests

  • a. In scope

  • b. Not in scope or in progress

  • c. Test Execution Metrics

• Known Issues

• Critical Issues

• Acronyms

Scope

MOSIP 1.1.5 succeeds 1.1.4 with enhancements and important defect fixes which were identified in Release 1.1.4.

We have also released some patch versions on top of 1.1.5, kindly view our patch documentation for the same.

Release Date: April 23, 2021

Key Highlights

• Enhancements

• Defect fixes

• Patch versions

Documentation

1. Platform

Includes functional requirements, process flows, architecture and high level design.

Link to documentation.

2. APIs

All APIs are documented here.

3. Design

Low level design documents for each module are available in the respective github repos.

Code

• Commons

• Pre-registration

• Registration Client

• Registration Processor

• ID Repository

• ID Authentication

• Partner Management Services

• Resident Services

• Admin Services

• Print Services

• Config Respository

• Durian

• Reference Implementation

Tests

a. In scope

Sanity of all modules, integration testing covering all modules, new stories , bug regression, upgrade from 1.1.4 to 1.1.5

b. Not in scope

c. Test Execution Metrics

Known Issues

The top issues identified in MOSIP 1.1.5 are listed below.

Upgrade Testing

Upgrade was done from 1.1.4 to 1.1.5 , below critical issues were identified and are still open.

Acronyms

Overview

The 1.1.5.5 version of MOSIP is a patch release on top of MOSIP's earlier intermediate patches released. This patch has many important bug and performance fixes which are backported from our LTS release.

This release also contains includes some new features such as the alpha version of MOSIP's first mobile application for residents and anonymous profile which are also backported from our LTS release.

Repository Released

Modules

Registration Processor

• Bug Fix: In some of the stages in the registration processor, we were using class-level variables due to which packets marked as “supervisor rejected”, were getting processed. Hence, we have removed the use of class-level variables in the registration processor.

• Upgrade: The maximum number of landing zones that can be added by an implementor has been increased from three to ten. #MOSIP-15978

• Performance Fix: In the registration processor, now we are creating a rest template only once and reusing it for every request to avoid performance issues. #MOSIP-15712

• Bug Fix: It was observed that the ABIS Handler stage is getting multiple requests for the same RID. Hence, we have added a fix to ignore duplicate requests coming for the same RID in the ABIS handler stage. #MOSIP-16638

• Bug Fix: In the case of an insert request, if ABIS sends an error stating that the reference ID is already existing in its gallery, then we are considering it to be a successful response. #MOSIP-14191

• Bug Fix: During packet processing, if a packet is missing in the landing zone we were throwing an error stating that the packet was not found, but if a packet is being reprocessed from the beginning of the militarized zone (from the secure zone notification stage) then the packet might be available in the object store and is deleted from the landing zone. Hence, before throwing the error we are now checking if the packet also exists in the object-store. #MOSIP-17290

• Bug Fix: In demo deduplication, now we have added a check to filter out potential duplicates without biometric reference IDs when we go for bio-match in ABIS. In scenarios where a resident is updating only demographic data there is no record for ABIS, hence, if demo duplicates for such records, then, we wouldn’t be able to perform bio-match in ABIS. #MOR-133

• Performance Fix: The performance of the reprocessor query has been improved by removing the use of DISTINCT in the query. #MOSIP-17860

• Bug Fix: When packets are getting reprocessed in the UIN generator stage, then the system is generating a new perpetual VID and revokes the old one (if VID is already generated). Hence, we have added a check to verify if a perpetual VID is existing before generating a new one. #MOSIP-14704

• Upgrade: An option to enable and disable packet processing from the secure zone notification stage based on a configuration has been added. This would help us throttle the records coming from the field using the reprocessor. #MOSIP-12276

• Upgrade: An option has been added to stop the processing of packets at any stage based on the configured bus out the address. This would help MOSIP implementors to throttle records based on their desired stage. #MOSIP-18534

• Bug Fix: Proper error handling in the packet receiver has been provided to avoid errors due to database null pointer constraint in the registration transaction table. #MOSIP-20110

• Bug Fix: A new configuration has been added to disable audit in the registration status service library to avoid VertX thread block. #MOSIP-19982

• Bug Fix: It was observed that digital signature validation was failing for child and update packets. A fix was provided for the same (after updating to the latest IDA). #MOSIP-20580 #MOSIP-20615

• Bug Fix: Packets with fingerprint authentication of operators were getting stuck. A solution has been added for this. #MOSIP-20867

• Upgrade: Health check endpoints have been enabled for printing, packet validator and abis middleware stages. #MOSIP-15842

• Bug Fix: Unnecessary storage of temporary files has been removed in the packet receiver stage. #MOSIP-12261

• Bug Fix: The child packet was getting rejected when the parent/guardian packet was in the queue for manual verification. Code has been modified to reject child packet only when parent/guardian packet is rejected. #MOSIP-20634

• Bug Fix: The request for kernel notification service from the registration processor notification service has been modified to prevent URL encoding errors. #MOSIP-21070

• Bug Fix: Code changes have been added to retrieve documents from data share while performing manual adjudication. #MOSIP-20837

Registration Client

• Bug Fix: In the 1.1.5.4 version of the registration client, the operator was not able to complete the registration when the applicant had a biometric exception as in some scenarios the operator is not able to see the exception photo capture. #MOSIP-15873

• Bug Fix: In the 1.1.5.4 version of the registration client, the operator was not able to complete the registration when the applicant has a biometric exception even though all the biometrics and exception photo was captured. #MOSIP-15871

• Bug Fix: In the 1.1.5.4 version of the registration client, the label for any attribute having a “date” and “ageDate“ control type was not visible. #MOSIP-15910 #MOSIP-15909

• Bug Fix: In the 1.1.5.4 version of the registration client, the operator was not able to move to the packet upload screen in offline mode, hence, he/she was not able to perform packet export. #MOSIP-16356

• New Feature: Support for multiple user logins in the registration client from different windows user accounts has been added. So, if two users are using the same windows, and the registration client is placed in a shared location, now both the user can log in to the registration client but please note that the same application cannot run simultaneously in two accounts. #MOR-113

• Upgrade: The data type for the value_json field in the dynamic fields table has been updated to CLOB so that we don’t have size limitations for dynamic fields. #MOR-134

• Bug Fix: Multiple fixes were made on the document scanner page to resolve performance issues while scanning documents. The features related to resource(webcam) handling, closing stream, and releasing webcam after capture were fixed.

• Upgrade: Taking max and min heap size as command-line arguments

• Bug Fix: Unable to launch registration client when upgrading from 1.1.5.4 to 1.1.5.5 as some of the new columns were missing. Hence 1.1.5.5 DB upgrade scripts were added. #MOSIP-20825

• Bug Fix: On restart of the registration client the local manifest was not replaced with the server manifest if the local and server version was the same. Hence the minor upgrade in the registration client was not working as expected. #MOR-148 #MOSIP-20824

• Bug Fix: If the registration client was failing to identify any document scanning devices or failing to load morena manager, the operator was not able to proceed further from the demographics page. This has been fixed - the operator would be able to proceed to the document scanning page.

• Bug Fix: Local dedupe check was working during registration because of a code issue. The fix has been provided.

• Bug Fix: Demographics and document page were getting overlapped when navigating back from preview page to documents page. #MOSIP-20474

• Bug Fix: In the biometrics details page the captured 'exception photo' disappears if navigating back to the previous screen due to which the operator had to recapture the exception photo. This has been fixed. #MOSIP-20868

Commons

• Performance Fix: We have modified the current base64 encoding and decoding implementation to JAVA’s native base64 codec because it performs better than the Apache base64 codec (the current implementation). #MOSIP-17298

• Performance Fix: The “exists()” method in the Khazana S3Adaptor implementation has been modified to be more performant. #MOSIP-17290

• Performance Fix: JAXB Context is instantiated every time in kernel core. And it is observed that 10% of the time is spent on instantiating the JAXBContext for BIRType class in IDA e-KYC. As JAXBContext is thread-safe, we are now initializing it once and reuse to avoid performance issues. And this fix is implemented in all the methods of the CbeffValidator class. #MOSIP-17991

• Upgrade: A health check has been added for the ID generator service

• Upgrade: A health check has been added for PRID generator #MOSIP-15845

• Upgrade: The notification service is updated by adding HTML support in the body of the email which is default by true and can be turned off by making “mosip.kernel.mail.content.html.enable” property to false.

Audit Manager

• Bug Fix: The reference ID type and reference ID in the kernel audit manager service were made mandatory whereas in the database these columns were optional leading to frequent errors in the service while storing the audit transactions. This has been fixed by modifying the audit manager. #MOSIP-18878

• Performance Fix: “The validation factory in audit manager is built for every request and it uses 70% of the processing time for audit calls”. Hence, we are now creating a single instance of the validation factory during the start-up of the audit manager and we are using it for all the audit calls. #MOSIP-17565

Open-ID-Bridge

• Upgrade: The kernel core dependency in kernel-auth-adaptor has been updated.

• Performance Fix: The config server health check from the kernel auth adapter has been disabled because every time the health check for the config server was called it was downloading some of the configuration files and was taking around 2 seconds to respond. #MOSIP-18380

• Performance Fix: In the validate token API of kernel-auth-service, JWT token decoding is performed in three different places which consume 10% of the time, we have restructured the code to decode the token only once to improve the response time by 6%. #MOSIP-17980

• Upgrade: Removed DB properties need for auth manager application. Auth manager is not using any database but due to the old configuration, it needs the database properties to start the application.

• Upgrade: RestIntercepter @component annotation removed to create a manual bean to not let it register to all RestTemplates. Authmanager was using two tokens in a single request which was creating auth failures.

WebSub

• Upgrade: Websub design is modified to a new Kafka based implementation.

• Upgrade: The web-sub client has been upgraded - for the Kafka based web-sub implementation.

Key Manager

• Database Update: In “keymgr-key_alias” table a new column cert_thumbprint character varying(100) has been added.

• Bug Fix: Added functionality to get individual id by user id to resolve the issue in performing user onboard in registration client.#MOSIP-20748

• Upgrade: Added support to decrypt using the master key in the key manager

• Performance Fix: Fixed performance issues in decryption & trust store creation.

Admin Services

• Upgrade: Fix for identity schema in admin service has been added for backward compatibility with 1.1.4 identity schema related to changes in language code attribute in the validator.

• Upgrade: Sync of gender and resident status was enabled in the sync data service to provide backward compatibility with the 1.1.4 version of MOSIP. #MOSIP-17282

• Performance Fix: Cache has been added for the sync data service due to the high response time observed for a few APIs. #MOSIP-17554

• Upgrade: The download of device details has been added in sync for backward compatibility with the 1.1.4 registration client.

• Upgrade: Websub client version has been updated for connecting with the Kafka based WebSub. #MOSIP-17735

• Upgrade: Kernel core version has been updated for the apache base64 codec library used in the kernel has performance issues. #MOSIP-18392

• Bug Fix: Error in pre-registration booking appointment when the registration centre selected has location hierarchy!= 5. #MOSIP-17754

• Bug Fix: Issue when we create a location with the same name with different parents in the same hierarchy level. #MOSIP-19954

Artifactory Reference Implementation

• Upgrade: Added a new artifact to docker file cache-provider-redis

• Upgrade: The latest mock-SDK is now being used for the latest bioSDK server

• Upgrade: The latest auth adapter is now being used for the 1.1.5.5 services

• Upgrade: The latest bioSDK client is now being used for internal mock bioSDK server implementation

Durian

• Bug Fix: Token expiration issue was resolved by deleting the expired token from the cache and fetching the new token and storing it in case of authentication failure. #MOSIP-17599

ID Authentication

• Upgrade: The thumbprint sent in the e-KYC response would be now HEX encoded and upper case. #MOSIP-16654

• Bug Fix: In the 1.1.5.4 version of IDA, when multiple fingerprints were sent to IDA for authentication it was found the system was throwing a hash validation error, which has been fixed. #MOSIP-17106

• Performance Fix: The e-KYC endpoint has been moved to the authentication service to make the e-KYC service more performant. #MOSIP-16870

• Performance Fix: Started using the JAVA’s native base64 codec encoder and decoder for base64URL encoding and decoding throughout IDA. Base64 URL safe encoding is used for all the API calls except encoding of BDB value inside the CBEFF file where Base64-Plain encoding is used. #MOSIP-16784

• Performance Fix: Added fixes to avoid repeated instantiation of WebClient in RestHelper implementation.

• Upgrade: Websub client version has been updated for connecting with the Kafka based web sub. #MOSIP-17735

• Performance Fix: Until the 1.1.5.4 version of MOSIP, all the biometrics were decrypted and decoded for biometric authentication leading to a higher response time. Now, we are encrypting all the modalities separately and storing - them so that only specific biometric types can be decrypted and decoded during authentication. #MOSIP-17300

• Performance Fix: Until the 1.1.5.4 version of MOSIP, all the demographic attributes were decrypted for demographic authentication and e-KYC leading to a higher response time. Now, only the required attributes are decrypted and decoded. #MOSIP-17302

• Performance Fix: In 1.1.5.4 we were storing the biometric data in IDA we were storing double encoded biometrics leading to double decoding during authentication. Now we have stopped doing double encoding in credential issuance for better performance.

• Bug Fix: Fix has been provided to allow attributes missing in the IDA mapping JSON file for authentication and e-KYC.

• Bug Fix: Fix for issue in returning auth token in response based on partner policy.

• Upgrade: We have moved to the latest key manager is IDA. #MOSIP-17523

• Performance Fix: We have optimized database calls during OTP authentication.

• Performance Fix: MOSIP-18523 - Added Caching for Salt during Auth

• Performance Fix: The logic for getting the salt key from the UIN/VID is optimized

• Database Update: We have added a few indexes in the IDA database for better performance.

• Database Update: In “ida-key_alias” table a new column cert_thumbprint character varying(100) has been added.

Partner Management Services

• Upgrade: Websub client version has been updated for connecting with the Kafka based web sub.

• Security fix: log4j dependencies have been removed.

Pre-registration services

• Bug Fix: Captcha Service is not working in 1.1.5.x version of MOSIP. #MOSIP-16977

• Performance Fix: We were observing high response times for the "/preregistration/v1/applications/config'" API. #MOSIP-16660

• Performance FIx: In the pre-registration application service, a new RestTemplate was created for every request. This has been fixed, only one rest templated is created and it is re-used. #MOSIP-18156

• Security Fix: In preregistration, the authorization tokens are being received from the server for even Wrong OTPs. #MOSIP-18903

• Performance Fix: Storing pre-registration in a single bucket instead of storing in multiple buckets per PRID has been added with backward compatibility.

Pre-registration booking service (reference implementation)

• Security Fix: Delete Appointment endpoint is not checking if the PRID belongs to the user in the token or not. #MOSIP-20309

Pre-registration UI service

• Bug Fix: In 1.1.5, the edit demographics page was not working in pre-registration when we did not have fullName in ID Schema. #MOSIP-15872

• Bug Fix: In 1.1.5 pre-registration, dynamic fields were not called using pagination. #MOSIP-15317

• Bug Fix: Captcha Service was not working in 1.1.5.x version of MOSIP. #MOSIP-16977

Print Service

• Upgrade: Websub client version has been updated for connecting with the Kafka based web sub.

ID Repository

• New Feature: Ability to generate verifiable credentials as part of MOSIP credential issuance #MOSIP-19079

• New Feature: Support for Anonymous Profiling #MOSIP-18179

• Bug Fix: Support for resident services to update the status of VID

• Performance Fix: Instead of publishing biometric data of individuals in a single CBEFF file, data is split and sent to IDA #MOSIP-17300

• Performance Fix: Primary key constraint error seen for few requests in ID repository add identity API #MOSIP-19422

• Performance Fix: Caching of salt tables in IDRepo

• Performance Fix: To compute a salt key, instead of performing modulo operation, substring operation has been done #MOSIP-18522

• Upgrade: The WebSub client version has been updated for connecting with the Kafka based WebSub.

• Upgrade: kernel-biometrics-api version has been upgraded to the latest version.

• DB Change: Added anonymous_profile and channel_info tables.

Resident Services

• Bug Fix: The “individual ID” and “individual ID Type” were taken twice as input for revoking a VID. #MOSIP-15969

• Bug Fix: Fixed update of resident data which not working as expected. #MOSIP-19917

• Bug Fix: Fixed issue while revoking VID. #MOSIP-19916

• Bug Fix: Fixed issues related to jackson dependency.

• Bug Fix: Encrypted HMAC IDA internal auth in resident should be base64-URL-safe encoded. #MOSIP-17931

• Performance Fix: Started using the JAVA’s native base64 codec encoder and decoder for base64URL encoding and decoding throughout Resident. #MOSIP-18026

Mobile ID Application (alpha-version)

• Functional documentation

• User Guide

• Open bugs:

  • If resident data is captured in multiple languages and in the data share policy, if the language filter is not specified for language-dependent attributes, the same is not displayed properly in the application. The impact of this issue is that the current version of the app displays credential data only in the language specified in the filter attribute set in the policy.

  • The set of resident attributes shown in the credential is not easily customizable and a change would require code modification.

  • While downloading a credential if an error is thrown in the UIN/VID selection page, the dropdown selection does not work properly and does not clear previously entered values.

This document contains the bugs that were fixed as part of MOSIP 1.1.4 release.

Overview

Release Version: 1.1.5.5-P1

Support: Patch Release

Release Date: 13-July, 2023

The 1.1.5.5-P1 release of MOSIP is a patch release which mainly focuses on performance improvements over the 1.1.5.5 version. This release also includes minor bug fixes.

Bug fixes

The link below contains the list of bugs/ issues that have been addressed as a part of this patch release.

To know more, refer Bug fixes for 1.1.5.5-P1.

Repository Released

Test Report

The detailed Test Reports are available at 1.1.5.5-P1 Base platform verification.

This document contains the bugs that were fixed as part of MOSIP 1.1.5 release.

Table Of Contents

Scope

Release Date: February 10, 2021

Key Highlights

Documentation

1. Platform

Includes functional requirements, process flows, architecture and high level design.

2. APIs

3. Design

Low level design documents for each module are available in the respective github repos.

Code

Tests

a. In scope

Basic integration testing was done covering the below modules.

b. Not in scope or in progress

c. Test Execution Metrics

Known Issues

The top issues identified in MOSIP 1.1.4 are listed below.

Acronyms

Table Of Contents

Scope

Release Date: October 24, 2020

Key Highlights

We have migrated from Java 8 to Java 11 as part of this release and also incorporated some software infrastructure changes as part of paring the technical debt.

Documentation

1. Platform

Includes functional requirements, process flows, architecture and high level design.

2. APIs

3. Design

Low level design documents for each module are available in the respective github repos.

Code

Tests

a. In scope

Basic integration testing was done covering the below modules.

b. Not in scope

c. Test Metrics

d. Test Execution Report

Acronyms

Table Of Contents

Scope

Release Date: December 14, 2020

Key Highlights

Documentation

1. Platform

Includes functional requirements, process flows, architecture and high level design.

2. APIs

3. Design

Low level design documents for each module are available in the respective github repos.

Code

Tests

a. In scope

Basic integration testing was done covering the below modules.

b. Not in scope or in progress

c. Test Execution Metrics

Known Issues

The top issues identified in MOSIP 1.1.3 are listed below.

To see all open defects, see https://mosip.atlassian.net/issues/?filter=10709

Acronyms

This document contains the bugs that were fixed as part of MOSIP 1.1.3 release.