Release Number: v.1.4.1
Release Date: 15th July, 2024
This release introduces new features centered on Verifiable Credentials (VC) issuance plugins related to Sunbird RC, enhances configuration capabilities for Knowledge-Based Identification (KBI), and addresses critical known issues from previous versions.
1. Features included
We have developed two new plugins to support the issuance of verifiable credentials (VC) by authenticating users through Knowledge-Based Identification (KBI) using the Authenticator plugin. These enhancements are detailed below:
a.
Implementation of the Authenticator plugin to enable Knowledge-Based Identification (KBI) within Sunbird RC.
b.
Implementation of the VC Issuance plugin to facilitate the issuance of verifiable credentials within Sunbird RC.
c. .
eSignet UI now supports KBI form configuration, making it easier to set up and manage KBI-based identification.
For more information on KBI, please refer to the
Improved Input Field Validations: Enhanced input field validations using regex implementation.
User-Friendly Error Messages: Improved error messages for better user experience.
eSignet Service Fixes: Critical and major bug fixes related to the eSignet service.
eSignet Signup Service Fixes: Critical and major bug fixes related to the eSignet Signup service.
For a complete list of all bugs addressed in this release, please refer to the .
Key Known Issue:
Please refer to for the list of all known issues.
For details on deployment, refer to the in the eSignet repository.
digital-credential-plugins
Intermittent issue faced in Biometric Login when used in certain organization/domain specific laptops.
eSignet
mosip-config
esignet-mock-services
mosip-ref-impl/kernel
artifactory-ref-impl
eSignet Signup
The scope of testing is to verify fitment to the specification from the perspective of
â—Ź Functionality
â—Ź Deployability
â—Ź Configurability
â—Ź Customizability
Verification is performed not only from the end user perspective but also from the System Integrator (SI) point of view. Hence, the Configurability and Extensibility of the software is also assessed. This ensures the readiness of software for use in multiple countries. Since MOSIP is an “API First” product platform, the Verification scope required comprehensive automation testing for all the MOSIP APIs. An automated Test Rig is created for the same.
Persona based approach has been adopted to perform the IV&V, by simulating test scenarios that resemble a real-time implementation.
A Persona is a fictional character/user profile created to represent a user type that might use a product/or a service in a similar way. Persona based testing is a software testing technique that puts software testers in the customer's shoes, assesses their needs from the software, and thereby determines use cases/scenarios that the customers will execute. The persona's needs may be addressed through any of the following.
â—Ź Functionality
â—Ź Deployability
â—Ź Configurability
â—Ź Customizability
The verification methods may differ based on how the need was addressed.
For regression check, “MOSIP Test Rig” - an automation testing suite - is indigenously designed and developed for supporting persona based testing. MOSIP Test Rig covers the end to end test execution and reporting. The end to end functional test scenarios are written starting from pre-registration, to the creation of the packet in the registration center, processing the packet through the registration process, generating UIN, and authenticating identity using IDA through various permutations and combinations of cases being covered. MOSIP Test Rig will be an open source artifact that can also be enhanced and used by countries to validate the SI deliveries before going live. Persona classes include both negative and positive personas. Negative persona classes include users like Bribed Registration Office, Malicious Insider, etc. The needs of positive persona classes must be met, whereas the needs of negative persona classes must be effectively restricted by the software.
Verification is performed on various configurations as mentioned below
â—Ź Default configuration - with 7 Lang (English/Khmer/Hindi/Kannada/Tamil/Arabic/French).
Signup Portal
Login with Password
Forgot Password
Login with OTP
Below are the test metrics by performing functional testing using mock MDS, mock Auth, and mock ABIS. The process followed was black box testing which based its test cases on the specifications of the software component under test. The functional test was performed in combination with individual module testing as well as integration testing. Test data were prepared in line with the user stories. Expected results were monitored by examining the user interface. The coverage includes GUI testing, System testing, End-To-End flows across multiple languages and configurations. The testing cycle included the simulation of multiple identity schema and respective UI schema configurations.
Test Rate: 99% with Pass rate: 97%
Here is the detailed breakdown:
API Based Testing - eSignet
Total Test Cases: 1601
Passed - 1555
Failed - 44
Skipped - 2
UI Based Testing
Total Test Cases: 664
Passed - 636
Failed - 15
Skipped - 13
Total Test Cases: 1116
Passed - 1111
Failed - 3
Skipped - 2
Below are the detailed test metrics by performing manual/automation testing. The project metrics are derived from Defect density, Test coverage, Test execution coverage, test tracking, and efficiency.
The various metrics that assist in test tracking and efficiency are as follows:
â—Ź Passed Test Cases Coverage: It measures the percentage of passed test cases. (Number of passed tests / Total number of tests executed) x 100.
â—Ź Failed Test Case Coverage: It measures the percentage of all the failed test cases. (Number of failed tests / Total number of test cases executed) x 100.
SubirdRC Integration (Using InjiWeb)
2265
2191
59
15
