Bug Fixes
This document contains the bugs that were fixed as part of MOSIP 1.1.3 release.
Password and Iris login screen overlay if auth token expires, and unbale to do password login to get fresh auth token
Registration Client
Packet is getting failed at OSI (ida internal service time out error a OSI stage)
Registration Processor
Packets are failing at validator stage(Unknownexception occured RPR-RCT-001 --> Unknown resource provided; nested exception is org.springframework.web.client.HttpServerErrorException: 500 )
Registration Processor
1.1.3-On-boarding authentication is not working in Registration Client
Registration Client
1.1.3- A packet is getting failed at OSI stage stating that Unable to access API resourceRPR-RCT-001 --> Unknown resource provided; nested exception is org.springframework.web.client.HttpServerErrorException: 500
Registration Processor
Unable to book appointment as getting technical error on slot selection page
Pre-registration
Bio update packet is getting failed stating that UIN Updation failed - Invalid Input Parameter - documents - individualBiometrics
IDA / ID Repository
Reg-Client getting hanged when consent proof is selected for scan in Document upload page
Registration Client
Getting error "RES-SER-009" while trying to lock the Auth using Perpetual VID
Resident Services
Unable to test update and child packet flow-Unable to access API resourceRPR-RCT-001 --> RPR-RCT-001; nested exception is org.springframework.web.client.HttpClientErrorException: 404
Registration Processor
1.1.3:: Two instances of Reg Client are running, one is reg-client and another one is the launcher.
Registration Client
Getting error RES-SER-020 while updating the resident demographic details from resident service
Resident Services
1.2 Reg Client with Mock MDS:: Biometric login, packet auth, and EOD auth are not working for the thumb.
Registration Client
1.2 Reg Client with Mock MDS:: Biometric login, packet auth, and EOD auth are not working for Right Hand Fingerprint.
Registration Client
Unable to do KYC auth with demographic Details , however Demo_Auth is working
IDA / ID Repository
1.2 Reg Cli with Mock MDS :: Continue button is disabled if low threshold biometrics are captured with Mock MDS
Registration Client
Reg Client1.1.2 with Mock MDS:: Packet with Officer auth says Biometric file validation failed for officer in Reg Proc.
Registration Client
1.1.2Reg Cli with Mock: only a little finger is captured for officer/supervisor packet auth.
Registration Client
Child Packet failing in OSI stage with message "Biometric data - Iris did not match"
Registration Processor
Unable to sentOTP when user is performing send OTP with different transactionID
Resident Services
The application still present on the Your application page even after discard
Pre-registration
Error during send a notification to resident after packet validation stage.
Registration Processor
ObjectStore should return boolean instead of throwing exception when exists method is invoked
Commons
1.1.2(MOCK MDS ): Packets are still displayed in the Pending approval list though EOD auth is successful (it mean EOD auth with a bio is not working as expected).
Registration Client
Hide document screen if the entire document section is removed from UI spec.
Registration Client
WebSub subscrtiption secret should be accepted from property in intent verification annotation
Commons
Unable to continue to biometric screen after scanning the document ( workaround works)
Registration Client
1.1.2 - Packet is failing at BIOGRAPHIC_VERIFICATION stage stating that Unknown exception occured null.
Registration Processor
The id sent in the .csv file is getting save for the tables where unique id is generated when data is sent
Admin Services
1.1.2 -Unable to Create New/Update Packet when Document Scanner is Enabled.
Registration Client
1.1.2: Very frequently minio returns object as null ( during search and packet processing )
Registration Processor
The user is not redirected to list view page under center, device and machine
Admin Services
The demo details filled during registration in Reg-client is not shown on the preview, acknowledgement and approval page.
Registration Client
Getting error errorCode": "KER-MSD-311",while trying to search Location data
Admin Services
We are able to change the status of the device which is in Revoked state to Registered
Admin Services
1.1.2: Sync failure as client id/secret key authentication is failed because the secret key is plaintext {Cipher}.
Registration Client
1.1.2 -In All Env - All the reg proc pods need to be restarted multiple times to bring up reg proc completely (Packet stuck at any stage at any time).
Registration Processor
Default name is missing in UIN update template when any demo filed is updated excluding name.
Registration Client
Officer / Supervisor biometric data is not sent in the meta_info.json (Packet is getting failed in the OSI stage).
Registration Client
On every launch Reg Client asks for the update though no update is there.
Registration Client
The inactive Center type is shown in the drop down Registration center type in center creation and Update form
Admin Services
Last updated
Was this helpful?