1.2.0.1-B1 (Beta)

Overview

Release Name: 1.2.0.1 Beta1

Release Version: 1.2.0.1-B1

Support: Developer Release

Release Date: 14-Oct 2022

The 1.2.0.1 Beta release of MOSIP is the first patch release on top of the Long-Term Support (LTS) release 1.2.0. This patch release mainly contains the fixes for bugs, security and performance. This release also contains minor feature enhancements. One of the major highlights of this patch release is the V3 deployment. Support for legacy V2 deployment is deprecated. The recommended deployment method will be V3 deployment architecture.

Repository Released

Repositories	Tags Released
commons	v1.2.0.1-B1
mosip-openid-bridge	v1.2.0.1-B1
audit-manager	v1.2.0.1-B1
keymanager	v1.2.0.1-B1
khazana	v1.2.0.1-B1
packet-manager	v1.2.0.1-B1
admin-services	v1.2.0.1-B1
id-repository	v1.2.0.1-B1
pre-registration	v1.2.0.1-B1
id-authentication	v1.2.0.1-B1
registration	v1.2.0.1-B2
resident-services	v1.2.0.1-B1
admin-ui	v1.2.0.1-B1
registration-client	v1.2.0.1-B1
partner-management-services	v1.2.0.1-B1
mosip-config	v1.2.0.1-B1
print	v1.2.0.1-B1
websub	v1.2.0.1-B1
durian	v1.2.0.1-B1
partner-management-portal	v1.2.0.1-B1
mosip-ref-impl	v1.2.0.1-B1
artifactory-ref-impl	v1.2.0.1-B1
reporting	v1.2.0.1-B1
mosip-functional-tests	v1.2.0.1-B1
mosip-data	v1.2.0.1-B1
mosip-automation-tests	v1.2.0.1-B1
keycloak	v1.2.0.1-B1
biosdk-services	v1.2.0.1-B1
biosdk-client	v1.2.0.1-B1
mosip-infra	v1.2.0.1-B1
mosip-helm	v1.2.0.1-B1
mosip-file-server	v1.2.0.1-B1
postgres-init	v1.2.0.1-B1
mimoto	v1.2.0.1-B1

Modules

Commons

• Bug fix: Filter search was not working for the user zone and center mapping page. This error was because keycloak expected two different values for first name and last name and none of it should be null. As a fix, changes were made in keycloak. #MOSIP-18973

Administration

• Bug fix: In the admin UI, there was a restriction on the number of drop-downs as it was hardcoded and hence it wasn’t flexible. As a fix, the property-filterValueMaxCount:{"default":${mosip.kernel.filtervalue.max_columns},"registrationcenters":50,"locations":100} was added which has the ability to configure the number of items in drop-down. #MOSIP-19978

• Bug fix: Audit logs were not listed for few transactions. After the fix, audit logs were getting listed in the DB. #MOSIP-19965

• Bug_fix: In the admin portal, the cloning feature was not working. If a template had to be cloned from English to Arabic, on Arabic login, it displayed template not found error even though template was present. This issue has been fixed and cloning feature is now working. #MOSIP-19935

• Bug fix: User zone and center mapping column sort was not working as expected. As a fix, sorting for logical column was removed. #MOSIP-19934

• Bug fix: For bulk upload, the event Id in audit log was incorrectly being captured. After the fix, the audit logs displayed the expected event Id. #MOSIP-19841

• Bug fix: In admin portal, when the center is inactive, the user should still be able to change the zone. After the fix, user was able to change the zone with an inactive center. #MOSIP-19817

• Bug fix: In admin portal, for an active center, when a device was created in that center, on editing the device, it did not display the expected values (it was blank). After the fix, the device details are visible in edit mode. #MOSIP-19806

• Bug fix: In Arabic language, on selecting the location on 1st level of hierarchy, the value in 3rd level of hierarchy was being populated. After the fix, the value of only 2nd level of hierarchy is populated on selecting the location on 1st level of hierarchy. #MOSIP-19699

• Bug fix: In admin portal, when the status of a language dependent masterdata was changed or if it was decommissioned, in a particular language, it was expected to be reflecting in other languages as well. After the fix, it was reflecting in Arabic language as well. #MOSIP-19652

• Bug fix: For language dependent masterdata, both the code and lang_code should have primary_key_constraint so that one is able to have same code in different languages. As a fix primary_key_constraint was added. #MOSIP-18682

• Bug fix: Failure/Error messages are displayed with "!". In case of failures and errors, the exclamation symbol from the end of the text was removed to fix the issue.#MOSIP-18658

• Bug fix: In the existing dynamic field, the "name" and "description" field were editable. After the bug fix, those were made to be non-editable. #MOSIP-18589

• Bug fix: In the admin portal, when one adds values under an existing dynamic field, the description of that value should be pre-filled with the data in the existing dynamic field. After the fix, the description was auto-filled as expected. #MOSIP-18584

• Feature upgrade: While creating dynamic field, initially, we used to input the data as dataType and now it is entered as text field. #MOSIP-16855

• Bug fix: In admin portal, the pagination options were displayed in "English" language by default instead of the logged-in language. After the fix, pagination was displayed in the logged-in language.#MOSIP-16382

• Bug fix: In admin module, \tags were visible in the UI. After the fix, \tags were removed from the UI. #MOSIP-19979

• Bug fix: The audit logs were being logged in with incorrect event messages. As a fix, static audit logs were updated to fix the event messages. #MOSIP-19966

• Bug fix: In admin module, packet upload was failing. As a fix, data-read role was assigned to the user. #MOSIP-19818

• Bug fix: In Admin module, one was able to map Machine and Device to different Center ID which does not belong to that zone. As a fix, a validation was put in place to check if the center ID belongs to the given Zone or not. #MOSIP-19724

Registration Client

• Bug fix: Crop and Delete option was not working in Scan document window. After the fix, it was possible to perform the crop and delete action. #MOSIP-19431

• Bug fix: Capture Time not displaying in Supervisor/Operator Biometric screen in Registration Client. The “Capture Time” label is removed from UI. #MOSIP-18720

• Bug fix: In Registration Client, ""/"" Symbol is displaying before all Registration tasks. Removed slash before the registration tasks to fix the issue. #MOSIP-18649"

• Bug fix: UI should be refactored with RTL support when logged in Arabic language, after fixing the issue, able to see all the pages in RTL format when logged in Arabic. #MOSIP-18641

• Bug fix: In Registration Client, the biometric correction label was overlapping with the consent screen. As a fix, wrap text was enabled on label. #MOSIP-18077

Partner Management Services

• Bug fix: In PMP UI, the error message logo was missing. As a fix, error icon was added throughout the application. #MOSIP-19976

• Bug fix: In FTM details menu button, the name was "create device" instead of "create FTM". As a fix, the name of the button of resource bundle was modified to create FTM instead of create device. #MOSIP-19918

• Bug fix: In PMP UI, filter labels were not pointing to logged in language. As a fix, support was added to display label in multi language. #MOSIP-19639

• Bug fix: In PMP UI, filter columns for partner menu was not proper. As a fix, the display label was modified. #MOSIP-19414

• Bug fix: In PMP UI, user was allowed to create SBI details without mandatory details. After the fix, without mandatory details, SBI creation is not allowed. #MOSIP-17562

• Bug fix: In FTM details page, the status should be approve/reject instead of active/de-active. After the fix, approve/reject labels were updated. #MOSIP-19823

• Bug fix: In PMP UI, the partner could be mapped to the same policy twice. After the fix, one partner can only be mapped to one policy. #MOSIP-19773

• Bugfix: In PMP UI, when a partner is registering themselves, the partner Id should be one single word with no space. After the fix, partner Id was not allowed to be created with space. #MOSIP-19404

• Bug fix: In PMP UI, partial search was not working. After the fix, partial search was working with asterisk(*). #MOISIP-19347

• Bug fix: In PMP UI, the partner admin should not be allowed to change the SBI details and FTM details after it was approved. After the fix, the SBI details and FTM details were made uneditable. #MOSIP-19309

• Bug fix: In PMP UI, the expected error message when the SBI details are added to the pending status device details was "Device details are not yet updated" instead "Device details does not exist" was seen. As a fix, label was updated. #MOSIP-19306

• Bug fix: In PMP UI, Search box was case sensitive in partner policy mapping. After the fix, the Search was made to be case insensitive. #MOSIP-19289

• Bug fix: In PMP UI, if a partner tries to register using an email which already exists, instead of displaying "email already registered", it was showing a blank page. After the fix, it was correctly showing the message. #MOSIP-19277

Pre-registration

• Bug fix: Cancel application mails from pre-registration were not being sent and email templates were not being fetched from correct template type code. After the fix, the mail contents were fetched from respective templates and cancel mails were duly sent. #MOSIP-18192

• Performance fix: Booking Slots were missing for many centers in cellbox2 env. As a fix, a code change was done in Batch Job to call master data API with sorting by "ID" instead of "createdDateTime". #MOSIP-19942

• Security fix: The attacker could potentially see the files from the application or system. Using this, attackers can access other files as well. To mitigate the risk, the URL should not allow path manipulation. The "accept known good" input validation strategy was put in place. Also, a whitelist of acceptable inputs that strictly conforms to specifications was used. #MOSIP-14246

• Bug fix: When a center was created without selecting lunch hours, at the center selection page it was showing lunch time as 12:00 AM to 12:00 AM. As a code fix, a condition "if lunchStartTime!= lunchEndTime" was put in place. #MOSIP-18985

Comprehensive Review

• Bug fix: PACKET_NOT_FOUND_EXCEPTION packet reprocessed after deleting from the landing zone. Cherry-pick was missed out from older branches(1.1.5), hence the Dev team updated changes in 1.2.0 and now it is working as expected. #MOSIP-19651

• Bug fix: DMZ packet servers were not able to handle multiple landing zones. After the fix, DMZ packet servers were able to handle multiple landing zones. #MOSIP-19650Reporter

• Bug fix: UIN generation notification email has $name_eng in template body. In the database, the name is not mentioned as per the ID schema, after making appropriate changes, the name is coming correctly in the email notification.G87 #MOSIP-11872

• Bug fix: If a RID was inserted twice, referenceId already exists (in ABIS) error was displayed and the packet was being sent for reprocessing. After the fix, the packet was not passed onto the reprocessing stage. #MOSIP-14191

ID Authentication

• Bug fix: Even when DEVICE_PROVIDER Id was hot listed, authentication was being performed successfully. As a fix, Client secret key in property mosip.mosip.hotlist.client.secret was duly configured. #MOSIP-19829

• Bug fix: Even with an invalid document Id, UIN was getting activated. As fix a, in ID schema, subType attributes was added. #MOSIP-19338

• Bug fix: Authentication was successfully performed even with garbage value of application property of demo service as mosip.env. As a fix, the only allowed values were restricted to IDA authentication property files. #MOSIP-19160

• Bug fix: In the database, when e-KYC was performed, the entries were incorrect as OTP-AUTH, KYC-AUTH. After the fix, the entries are KYC, authentication type (E.g.: KYC-AUTH, OTP-AUTH). #MOSIP-18285

• Bug fix: In the database, the column called cr_by was not being updated and was left empty. This bug was fixed, cr_by column has the correct value of who created that particular entry. #MOSIP-14291

• Bug fix: Once the transaction configuration was changed to "2", the transaction limit in IDA DB did not change. After the code fix, the changes in config properties were being reflected in the DB. #MOSIP-19736

Resident Services

• Bug fix: Notifications were not being sent as per the preferred language. After the fix, notifications for send OTP were received in preferred language. NOTE- UINs generated from IDREPO. #MOSIP-19371

• Bug fix: VID was not behaving correctly according to the config properties. Also, OTP was successfully being sent even with a revoked VID. After the fix, both the above issues were resolved and behavior of VID was based on config and also OTP could only be sent with a valid active VID. #MOSIP-19270

• Bug fix: In the process of updating the demographic details of the resident from resident API, base exception errors were displayed. After the code fix, we were able to update the demographic details successfully. #MOSIP-19525

DB Changes

SchemaName.Table	Column name	Changes done	Description
master.loc_holiday	id	removed from composite primary key	This column doesn’t fit well in the primary key as it allows duplicate holidays on same day which is not expected.
master.loc_holiday	holiday_date	added to composite primary key	Adding this constraint restricts the user from creating multiple holidays on the same day.
master.blocklisted_words	lang_code	removed notnull constraint and dropped this column from composite primary key	Since the “word” column is enough to identify the word uniquely, there is no need for lang_code to be in primary key.
pms.ftp_chip_detail	approval_status	added	This column is added to track certificate upload and admin approval.
regprc.registration_list	ref_id	added	This attribute is needed for packet encryption/decryption.
prereg.processed_prereg_list	prereg_trn_id	dropped the Foreign Key constraint	The table to which the Foreign key was referring to did not exist.

Known Issues

To view the list of known issues, click here.

Note: The 1.2.0.1-B1 version of Registration Client will not support the latest mock MDS (1.2.1-SNAPSHOT). All the biometrics will be captured fine but exception photo capture fails. To know more, refer here.

Documentation

For complete documentation, refer to 1.2.0 LTS documentation.

Deployment documentation and scripts have been enhanced and are compliant with V3 architecture.

Developer documentation for repos have also been added for developers to setup in their local systems.