Release Name: Inji Wallet 0.14.0
Release Type: Developer
Release Date: Coming Soon
We are excited to announce the release of Inji Wallet Version 0.14.0! This update introduces major enhancements and new features, particularly in credential issuance. Here are the key highlights of this release:
PixelPass Enhancements: Support for CBOR encoding/decoding is available, making PixelPass more versatile and efficient in handling data.
Integration with Inji Certify: We've integrated eSignet for authentication and Certify for streamlined credential issuance, providing a seamless experience.
Compliance with Draft 13 of the OpenID4VCI Spec: Inji Wallet now fully supports the latest Draft 13 changes of the OpenID4VCI specification, ensuring compatibility with the evolving standards in the industry.
Java upgrade in mimoto: A significant tech upgrade for mimoto to move from java11 to java21.
PixelPass enhancements - Support CBOR encoding/decoding
Given JSON data, it does the CBOR encode/decode.
Given a JSON and a Mapper(similar to claim 169) are given, it maps the JSON with Mapper and then does the CBOR encode/decode.
Integrate eSignet for Auth and Certify for credential issuance
Authorisation partner: eSignet
KBI plugin: eSignet
Credential Issuance: Certify
Draft 13 changes of OpenID4VCI spec - Compatibility of the credential issuance as per the latest draft of OpenID4VCI specification.
The following table outlines the tested and certified compatibility of Inji Wallet 0.14.0 with other modules.
Below is the list of known issues. To read in detail and view all the issues related to Inji Verify please click here.
Note: Redmi devices are not supported in this release.
Below is the list of fixes as part of the 0.14.0 release:
QA Report
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 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, Verification scope required comprehensive automation testing for all the MOSIP APIs. An automation Test Rig is created for the same.
The Inji testing scope revolves around the following flows:
Biometric unlock
Passcode unlock
VC download via MOSIP
VC download via esignet
VC download via Sunbird
Pinning a VC
Normal VC sharing with VID
Deleting VC
Face Auth on Resident's phone with VID
Multi language support
Credential registry
Backup and restore
Wallet binding
QR code Login
Logout
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 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 - which 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 creation of packet in registration center, processing the packet through the registration processor, generating UIN and authenticating identity using IDA through various permutation and combinations of cases being covered. MOSIP Test Rig will be an open-source artifact which 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 3 Lang
Virtual countries
1 Lang configuration
2 Lang configuration
3 Lang configuration
On Android Device:
On iOS Device:
Below are the test metrics by performing functional testing using mock MDS 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 of 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 simulation of multiple identity schema and respective UI schema configurations.
Here is the detailed breakdown of metrics for each module:
The below section provides details on API test metrics by executing MOSIP functional automation Framework. All external API test executions were performed at module level isolation. Each end point is tested with the test data and expectations of each test data are mapped to assert the test case.
The below section provides details on Ui Automation by executing MOSIP functional automation Framework.
Here is the detailed breakdown of metrics
Functional and test rig code base branch which is used for the above metrics is:
Hash Tag:
SHA: sha256: 58e77d26fc1b98884c11638bba70c128d27994e3
Below are the test metrics by performing VC Sharing functionality on various device combinations
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 tests passed / 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
Jira issue | Issue description |
---|---|
Repositories
Tags Released
Inji-wallet
v0.14.0
Module
Version
Mimoto
v0.14.0
Inji-config
v0.3.0
eSignet
v1.4.1
Inji Verify
v0.10.0
tuvali
tuvali-ios-swift
secure-Keystore
pixelpass
pixelpass-ios-swift
Inji-vci-client
Inji-vci-client-ios-swift
Inji Wallet- After clicking the + icon, the screen flickers before landing on the 'Add New Card' screen
The search box close button is not working unless invoked on a specific point
Inji Wallet- Android - History timings could be more precise
IOS- The Wallet app session should expire if the app is opened for a longer time and the user tries to log in again with the PIN to generate VC by using UIN/VID.
Inji Wallet- The error message of QR code login without an internet attempt should be revised
Inji Wallet- On the face verification page the capture button overlaps with the text
Inji Wallet- During face authentication, the camera view is not opening in all IOS device
Inji Wallet - IOS - "Share QR Code" is not working on iPhone 8.
Inji Wallet - Backup is not triggering automatically when VC is removed.
Inji Wallet- the logo of Inji Wallet stretched while booting the app
IOS -For specific devices, the User cannot see the iCloud ID in the iCloud setting section of the backup and restore page.
Inji Wallet - An error message is not proper when an invalid QR is scanned after changing the language to something other than English.
Inji Wallet- Backup & restore Name Is Different In Settings And Backup & restore Page
Backup and Restore heading Alignment is not proper on the Backup& restore page
Inji Wallet- Sometimes VC activate the button and the back button responses are very slow
Inji Wallet- ID Repo UINs are failing in VC verification
Inji Wallet- Backup doesn't append the new data but replaces the data
Upon changing the finger authentication in the device, the application does not display the error pop-up for biometrics change
Jira issue
Issue description
Inji Wallet: When the camera access is disabled, the user clicks on the close icon error screen it redirects to the sharing screen
Inji Wallet - Unable to go back from the detailed view page
Inji Wallet- VC verification is passing for missing attribute VC
Inji Wallet- During face authentication, the camera view is wider than the face.
Inji Wallet - IOS - The "Share QR Code" feature saves both the QR Code and a text file to files.
Inji Wallet- Users are unable to upload the VC QR code shared via email and WhatsApp, or stored locally
Inji Wallet- In Android when the user clicks the + icon from the home page issuer page is not loaded
Inji Wallet - Unable to see the issuer of the credentials
Inji Wallet- Sunbird issuer is not loading and is redirecting to the 'Add New Card' screen. Trying to click any other issuer is also not working
Inji Wallet- The Intermittent share with selfie option is not getting for the National Identity department
Activation successful banner is not showing up
Inji Wallet- We are unable to download the VC Stay Protected insurance credential
Inji Wallet- When the Certify well-known is replaced with fall back well-known url in the Inji configuration The user is not redirected to the default well-known issuer
Inji Wallet- The user is not getting any error if the fallback is not working
Inji Wallet-Mock identity is not loading and is redirecting to the 'Add New Card' screen. Trying to click any other issuer is also not working
Activated option in quick access menu for VCs which doesn't have biometrics
Inji Wallet- In the mock VC, there is no profile photo, but the share option is still visible
When display properties are removed at mosip certify the user is blocked with a white screen and not able to use the app.
Update mimoto local properties file to run mimoto locally without docker-compose
Background colour not showing up in VC as per configuration in well-known
Total
Passed
Failed
Skipped (N/A)
2461
2203
214
44
Test Rate: 98.21% With Pass Rate: 91.14%
Test cases
On Android Device
Total
1315
Passed
1169
Failed
117
Skipped (N/A)
29
On iOS Device
Total
1146
Passed
1034
Failed
97
Skipped (N/A)
15
Total
Passed
Failed
Skipped
141
134
4
3
Test Rate: 97.97% With Pass Rate: 97.10%
Total
Passed
Failed
Skipped
108
106
2
0
Test Rate: 100% With Pass Rate: 98.14%
Test cases
Android
Total
60
Passed
58
Failed
2
Skipped
0
iOS
Total
48
Passed
48
Failed
0
Skipped
0
Total
Passed
Failed
Skipped
192
192
0
0
Test Rate: 100% With Pass Rate: 100%
Tested with Components
mosipid/esignet:1.4.1
mosipqa/mimoto:develop
Tuvali Version - 0.5.1
Tested with MOSIP Components
mosipid/admin-service:1.2.0.1-B1
mosipid/admin-ui:1.2.0.1-B1
mosipid/artifactory-server:1.4.1-ES
mosipid/authentication-internal-service:1.2.0.1
mosipid/authentication-otp-service:1.2.0.1
mosipid/authentication-service:1.2.0.1
mosipid/biosdk-server:1.2.0.1
mosipid/commons-packet-service:1.2.0.1-B1
mosipid/config-server:1.1.2
mosipid/consolidator-websub-service:1.2.0.1-B1
mosipid/credential-request-generator:1.2.0.1
mosipid/credential-service:1.2.0.1
mosipid/data-share-service:1.2.0.1-B2
mosipid/hotlist-service:1.2.0.1-B1
mosipid/id-repository-identity-service:1.2.0.1
mosipid/id-repository-salt-generator:1.2.0.1
mosipid/id-repository-vid-service:1.2.0.1
mosipid/kernel-auth-service:1.2.0.1-B2
mosipid/kernel-idgenerator-service:1.2.0.1-B1
mosipid/kernel-keymanager-service:1.2.0.1
mosipid/kernel-notification-service:1.2.0.1-B1
mosipid/kernel-otpmanager-service:1.2.0.1-B1
mosipid/kernel-pridgenerator-service:1.2.0.1-B1
mosipid/kernel-ridgenerator-service:1.2.0.1-B1
mosipid/kernel-salt-generator:1.2.0.1-B2
mosipid/kernel-syncdata-service:1.2.0.1-B1
mosipid/keycloak-init:1.2.0.1
mosipid/keycloak-init:1.2.0.1-B2
mosipid/keycloak-init:1.2.0.1-B3
mosipid/keys-generator:1.2.0.1-B3
mosipid/masterdata-loader:1.2.0.1-B4
mosipid/mock-abis:1.2.0.1-B2
mosipid/mock-mv:1.2.0.1-B2
mosipid/mock-relying-party-service:0.9.1
mosipid/mock-relying-party-service:0.9.2
mosipid/mock-relying-party-ui:0.9.1
mosipid/mock-relying-party-ui:0.9.2
mosipid/oidc-ui:1.4.1
mosipid/partner-management-service:1.2.0.1-B3
mosipid/partner-onboarder:1.2.0.1-B4
mosipid/pmp-ui:1.2.0.1-B1
mosipid/policy-management-service:1.2.0.1-B3
mosipid/postgres-init:1.2.0.1-B4
mosipid/pre-registration-application-service:1.2.0.1-B1
mosipid/pre-registration-batchjob:1.2.0.1-B1
mosipid/pre-registration-booking-service:1.2.0.1-B1
mosipid/pre-registration-captcha-service:1.2.0.1-B1
mosipid/pre-registration-datasync-service:1.2.0.1-B1
mosipid/pre-registration-ui:1.2.0.1-B1
mosipid/print:1.2.0.1-B1
mosipid/registration-client:1.2.0.1-B1
mosipid/registration-processor-common-camel-bridge:1.2.0.1-B1
mosipid/registration-processor-dmz-packet-server:1.2.0.1-B1
mosipid/registration-processor-notification-service:1.2.0.1-B1
mosipid/registration-processor-registration-status-service:1.2.0.1-B1
mosipid/registration-processor-registration-transaction-service:1.2.0.1-B1
mosipid/registration-processor-reprocessor:1.2.0.1-B1
mosipid/registration-processor-stage-group-1:1.2.0.1-B1
mosipid/registration-processor-stage-group-2:1.2.0.1-B1
mosipid/registration-processor-stage-group-3:1.2.0.1-B2
mosipid/registration-processor-stage-group-4:1.2.0.1-B1
mosipid/registration-processor-stage-group-5:1.2.0.1-B1
mosipid/registration-processor-stage-group-6:1.2.0.1-B1
mosipid/registration-processor-workflow-manager-service:1.2.0.1-B1
mosipid/signup-service:1.0.0
mosipid/signup-ui:1.0.0
mosipid/softhsm:v2
mosipid/websub-service:1.2.0.1-B1
mosipint/digital-card-service:release-1.2.0.1-DP
mosipint/kernel-masterdata-service:develop-DP
mosipint/registration-processor-stage-group-7:develop-DP
mosipint/resident-service:develop-DP
mosipint/resident-ui:develop-DP
mosipqa/artifactory-server:0.9.0-INJI
mosipqa/artifactory-server:1.4.1-ES
mosipqa/authentication-demo-service:develop
mosipqa/automationtests:develop
mosipqa/dsl-orchestrator:develop
mosipqa/dsl-packetcreator:develop
mosipqa/inji-certify:0.9.x
mosipqa/inji-web:develop
mosipqa/kernel-auditmanager-service:1.2.0.1
mosipqa/keycloak-init:develop
mosipqa/mock-identity-system:0.9.3
mosipqa/mock-relying-party-service:0.9.x
mosipqa/mock-relying-party-ui:0.9.x
mosipqa/mock-smtp:0.0.2
mosipqa/mosip-artemis-keycloak:develop
mosipqa/mosip-file-server:develop
mosipqa/postgres-init:develop
mosipqa/softhsm:v2
Devices Used For Testing
Vivo Y73 with Android 12 BLE 5.0
SS Galaxy A03 core with Android 11 BLE 4.2
iPhone 11 with i-OS 15 BLE 5.0
iPhone 8 with i-OS 16 BLE 5.0
iPhone 7 with i-OS 15.6 BLE 4.2
Redmi 7A Android 10 BLE 4.2
Redmi note 10 lite Android 10 BLE 5.0
redmi K20 pro Android 11 BLE 5.0