v1.7.1
Release Number: v1.7.1 (Patch)
Release Date: Coming Soon
Overview
We are pleased to announce the release of eSignet v1.7.1, a patch release focused exclusively on addressing critical functional issues identified in earlier versions. This release improves stability and correctness across UI schema handling, KBI authentication flows, and deployment-related assets, ensuring a smoother and more reliable experience for integrators and deployers.
Major Highlights
Critical Bug Fixes
Fixed an issue in the UI schema where the email field was treated as mandatory even when configured as optional.
Resolved a problem where KBI login in mock services failed when CAPTCHA was enabled.
Addressed multiple issues related to deployment documentation, improving accuracy and clarity.
Fixed issues in partner onboarding scripts to ensure smoother setup and execution.
Bug Fixes
Several known issues from the previous release have been addressed to improve platform stability and performance.
Please refer to the link here for the complete list of resolved issues.
Partner onboarder issue in esignet-signup
Issue in partner onboarder esignet .
Update keycloak init scripts in esignet-signup
Update readme for partner-onboarding/esignet
Deployment : esignet readme does not contain delete steps Please Mention delete steps in readme
Deployment : softhsm for esignet is getting deployed in esignet ns but in the delete-all.sh its searching for softhsm which needs to be updated
eSignet- mosipid: “Unsupported language” error displayed on Forgot Password page when using Khmer language
Fix content for wallet_header on WLA login page
In Ui schema when email is marked as optional field by default its taking as mandatory field
Inji logo is not updated in esqa2
KBI login in mock is not working when captcha is enabled
eSignet - aud_claim in client-assertion is not accepting any three of par endpoint, token endpoint and issuer identifier.
FAPI 2.0 Compliance - Server accepted a cipher that is not on the list of permitted ciphers
Unable to create OIDC client from PMS endpoint from postman
In Android web browser, user can enter as many character as they want, it is not restricted by max length
Datatype mismatch in SBI Auth capture request
For the first capture the previousHash should be the SHA256 hash of an empty UTF-8 string
Known Issues
Please refer here for full list of known issues.
Partner onboarding fails due to existing records with no automated cleanup
eSignet-MOSIP & MOCK: When the user lands on the Network Error page, the browser Back and Forward buttons do not navigate to the previous or next pages.
eSignet-deployment: Missing Deployment Instructions for /mock-relying-party-ui, mock-relying-party-service in Documentation
eSignet-deployment: eSignet-with-Plugins Installation Script Missing OIDC Setup Steps
eSignet-deployment: End-User URL Not Clearly Defined for Cross-Cluster Module Dependencies
eSignet-Signup MOCK : Privacy Policy link navigates away from signup page instead of opening in new tab
Support both object and array for verified_claims request parameter
Repositories Released
Compatible Modules
eSignet with MOSIP compatibility matrix
eSignet with Sunbird compatibility matrix
Sunbird
Signup with MOSIP compatibility matrix
Documentation
API Documentation
Integration Guides
End User Guides
Last updated
Was this helpful?