Roadmap 2024
This page contains the product roadmap for MOSIP Identity for the calendar year January 2024- December 2024.
The quarters referenced below are defined as follows:
Q1: Jan24 - Mar24
Q2: Apr24 - Jun24
Q3: Jul24 - Sep24
Q4: Oct24 - Dec24
MOSIP Identity
Q1
Android Registration Client
Trust Validation
Test with real SBI
Transliteration
Audit
1.1.5.X compatible (change in decryption logic)
Usability fixes (UI changes for portrait mode)
Bug fixes
Completed
Q1
Biometric Enhancement
Block controls
Ability to perform liveness check
Comment
Block controls
Ability to compress the face photo
Comment
In-progress
Q1
PMP UI Enhancement
Planned
Q2
Android Registration Client:
Operator Biometric
Ability to update resident's Biometrics
Ability to access Dashboard
Hardening of DB
Ability to Transliterate (RTL)
1.1.5 compatibility
In-progress
Q2
Resident Portal:
Residents should be able to update their identity data, address data, and contact information
Residents should be able to access the Resident Portal in multiple languages
In-progress
Q2
Resident Portal:
Residents should be allowed to log into Resident Portal even when all their modalities are locked
Performance Testing
Features released in 0.9.0 release
Planned
Q2
Administrative Services
Digital ID features to be deployed in platform for General ID issuance.
Planned
Q2
ID Repository
Introducing Handles in Platform to:
ID Repository
Registration Client
Registration Processor
In-progress
Q2
Platform:
Renaming stage groups and regrouping the stages
Planned
Q3
Android Registration Client
Operator should not be able to create a resident's new registration packet using their own biometric
With operatorβs assistance, applicant should be able to successfully retrieve their lost UIN
With operatorβs assistance, applicant should be able to successfully update their UIN
Operator should be able to successfully export the packet created after successful registration of Applicant
Operator should be able to download pre-registration data onto Android Registration Client
Operator should be able to run Android Registration Client in landscape mode
Operator or Supervisor should be able to successfully logout from Registration Client
Operator should be able to run Android Registration Client on phone
Planned
Q3
Android Registration Client
Ability to support multiple centers
Ability to check for new updates/ version
Ability to set a new password if user has forgotten the password
Ability to reset the password
Ability to access settings section
Ability to modify machine-center remapping
Planned
Q3
ID Authentication:
Support ECC based digital signature and encryption
Planned
Q4
Android Registration Client
Keyboard in different languages
Telemetry
Support for 3rd party SDK to measure quality of biometrics captured
Add parameters and Add filters to Dashboard
Enhanced UI messages
Planned
Q4
Administrative Services
Digital ID features will be deployed in the platform for General ID issuance.
Planned
Q4
ID Repository:
Implementation of pixel pass
Planned
Q4
Platform:
Remodeling draft API creation
Planned
Q4
Platform:
Implementation of supporting array values for demo fields
Planned
Q4
Platform:
Capturing supervisor ID while packet creation
Planned
Q4
Platform:
Configuring demo fields for demo de-duplication
Planned
Q4
Platform
Revising Error messages to uniformly align error codes and error messages across all modules.
Wishlist
Q4
Platform:
Real time ID issuance
Wishlist
Q4
Platform:
Error message handling
Wishlist
Q4
Platform:
Notification Service - subscription /unsubscription
Wishlist
Q4
Platform:
Removing file server dependency
Wishlist
Q4
Platform:
Implementation of handles in pre-registration
Wishlist
Inji Stack
Click here to explore the Inji Stack Roadmap.
eSignet
Click here to explore the eSignet Roadmap.
Compliance Tool Kit (CTK)
Q1
SBI: Multi-factor Trust Validation with Organization Name Verification
Completed
Q1
SDK & ABIS: Capture vendor consent before uploading the biometric data in CTK
Completed
Q1
In SBI spec, add the ability to prompt for consent before collecting biometrics
Completed
Q1-Q4
Performance Testing
Evaluate performance benchmarks
Assess system response times, load handling, and overall efficiency
Planned
Q1-Q4
Refine the CTK Platform:
Identify areas of improvement
Prioritize refinements based on impact and feasibility
Planned
Partner Management System
Q2
Basic Features:
i) PMP:
a) Terms and Conditions page b) Partner Dashboard
c) User Profile
In-progress
Q2
Authentication Partner User Flow:
a) Partner certificate- upload, re upload, download original certificate, download MOSIP signed certificate, uploaded certificate details.
b) Policies - request policy, view, select policy group
In-progress
1.3.0-dp.1
Q2
Enable Authentication mechanisms for approved policies (Authentication Partner flow): a) API key generation- generate, view, deactivate b) OIDC Client creation- create, edit, view, deactivate
In-progress
1.3.0-dp.1
Q2
Keycloak Customization and Integration with PMS:
a) Login b) Registration c) Forgot Password
d) Verify Email
In-progress
Q3
Device Provider features: a) SBI -Device creation - add SBI, add devices, deactivate SBI, deactivate mapped devices b) Integration of common features- Partner Certificate Management
Planned
Q3
FTM Provider fetaures: a) FTM details- add FTM details, upload/ reupload/download FTM Chip certificate, deactivate FTM details
b) Integration of common features- Partner Certificate Management
Planned
Q3
Partner Admin: a) Partner Management- i) activate/deactivate partner, ii) add new partner iii) upload/re-upload CA certificate
b) Approve/ Reject device details c) Approve/ Reject FTM details
b) Policy Management- i) Add/rename/deactivate policy group, ii) Add/activate/edit/deactivate policy, iii) map/ approve/reject/deactivate partner policy mapping
Planned
Q4
Notification sent to user before expiry of partner certificate, CA Certificates
Planned
Q4
Multi User - Multi partner type management:
Partner Type Selection:
a) User- Add new partner type (applies to all users within same org) b) Admin- Approve/ Reject/ add new partner type within same org and also different org
User Management (in Partner Admin Portal)- approve/ reject/ Add new user / edit / view users
Partner Admin portal - Pending approval requests for partner type, new user , policy mappings
Planned
Automation
Q1
Dockerize the Admin UI test rig
Completed
Q1
Dockerize the Resident UI rig
Completed
Q1
Add multi-language support Resident UI test rig
Completed
Q1
Increase the DSL coverage for production scenarios
In-progress
Q1
Enhance the functional test rigs to reduce manual testing effort for new features
In-progress
Q1
UI test automation for Inji (Target environment iOS)
In-progress
Q1
Stabilize DSL test rig for consistent results across environments
In-progress
Q2
Component based functional test rig to be part of their corresponding component repository.
Planned
Q2
Enhance the functional test rigs to reduce manual testing effort for new features.
Planned
Q2
Increase the DSL coverage for production scenarios- Ongoing Activity
Planned
Q3
DSL should be able use DSL Test rig without any external resources. Currently, it consumes external mount volume (NFS).
Planned
Q3
Automate testing to reduce testing turn around time.
Planned
Q3
Convert Scenarios JSON to a standard cucumber (Gherkin Syntax).
Planned
Q4
Make Functional and DSL to consume biometric data mockMDS Authentication.
Planned
Q4
Create Listener for Web Sub Events and Credential Validation.
Planned
Q4
Enhance DSL to check for all notifications and their templates.
Planned
Last updated