Bug Fixes
This document contains the bugs that were fixed as part of MOSIP 1.1 release.
Kernel services are not working as kernel-masterdata-service pods are in CrashLoopBackOff
Commons
Valid tokens returned from TokenHandlerUtil are marked invalid when sent to Auth Manager
Commons
Kernel services are not working as kernel-masterdata-service pods are fauling in preprod environment
Commons
Updated keys are not present in Key_Store table after Master Sync in Registration Client
Commons
Sync configuration failing for a gap of 30 mins because of which packet was not uploading
Commons
Create and Update Machine have Issues related to optional and mandatory fields
Administration
Unable to validate document in arabic language but validation is possible with english language
Administration
Unable to create the registration center as throwing "ERROR: duplicate key value violates unique constraint"
Administration
Getting Technical error occurred on Admin UI when login to pre-reg on another tab of browser
Administration
Update machine: wrong error message when the zone code value is sent as blank
Administration
Update Reg Center API:wrong error message thrown for when Exceptional Holiday Date format is invalid
Administration
Update Document type API: wrong error message is displayed when the value for code is sent blank.
Administration
Holiday search API: Positive response is received even though sort-type field is sent with wrong value
Administration
Exception Holiday dates are not getting saved in the update form of a registration center
Administration
Register Device API is allowing to register a device with certification as L1 and without FTPId
Administration
Register Device API is allowing to register a device with invalid certification and purpose
Administration
Center Update Error - Secondary language details to be edited getting is not updated or saved in the center
Administration
UX standards Issue - UI implemented has deviations when compared to the expected standards
Administration
Language in the Blacklisted Detail View screen is displayed wrong when the word is other than English
Administration
Update MDS is not giving proper message in case of inValid regDType and regDSType
Administration
Register and Update FTP and MDS is not providing proper validation messages for many scenarios
Administration
Update Device provider is allowing to update a device provider to the existing device provider
Administration
When syncbyte vendor MDS version is changing and we creating pkt with this new mds, the dpid which is deviceprovideid inside the pkt is changing
Administration
Text of few of the labels in the Admin UI screens are not displayed in the language configured(French)
Administration
Exceptional Holidays added to a center is displayed as a blank field in the center detail screen
Administration
Wrong error message displayed when Fetch Execeptional Holidays for Reg center API is executed
Administration
Wrong error messages displayed when Fetch working days for Reg center ID API is executed
Administration
Create registration Center API is creating a center even if we are not passing working-Non-Working day for all days
Administration
Update RegCenter API allowing to update a center even if it doesn't belongs to admin zone or admin's child zones
Administration
Exceptional Holiday Dates already defined for the center is not visible in the Center detail screen
Administration
Field name is not displayed in the error message when request is sent in wrong format
Administration
Device Validate API is not doing deviceType and deviceSubType validation against device provider
Administration
Wrong response messages are displayed for mapping registration center~machine
Administration
Error is thrown when code field is sent as blank in document type POST request body
Administration
Update Location API is allowing to Deactivate parent location even if child location is active
Administration
Create Machine:Wrong error message is generated in response although optional field as sent as blank in the request
Administration
Create Machine:Wrong error message is generated in the response when invalid mSpec_id is sent in request
Administration
Wrong validation messages shown when "MAp user-Registration Center API" is executed
Administration
Wrong validation messages are displayed when "Un-Mapping the user from registration center"API is executed.
Administration
Wrong error messages are displayed in the response from Mapdevice to Reg center API
Administration
API_Bug:Wrong error messages received as Response which do not match the messages mentioned in acceptance criteria
Administration
API_Bug:The values to be updated in the statuscode is not logged in the DB tables
Administration
"API_Bug:Device status updated Successfully" message gets displayed even after providing the existing values for a particular device code in the request.
Administration
Register and Update Device provider Api is giving the wrong validation messages
Administration
Field length validation is not implemented in Register/Update Foundational trust provider API
Administration
Applying filters for Region,Province,Zone and city are cases sensitive. Filters are not getting applied if entered in upper or lowercase letters..
Administration
Adding filters by entering special chars in any free text fields will consider it as an valid search and displays the data.
Administration
Unable to move ahead from pre-reg demographic page - shows technical error and page keeps loading
Pre Registration
The value populating under zone and city is incorrect if the province field is delete and hierarchy is changed
Pre Registration
Unable to proceed further from Demographic page when the field is made non-mandatory using Json
Pre Registration
Pr-registration fully blocked with an error "Error creating bean with name 'referenceValidator'" - impacts further Pre-reg testing
Pre Registration
The tool tip message needs to be corrected In your application page under discard button
Pre Registration
The user is getting logout when click out side the Logout confirmation popup
Pre Registration
Under preview page the document uploaded remains same when minor is changed to Adult
Pre Registration
The Open days are not coming under booking appointment page when language is selected as arabic
Pre Registration
The demographic page become blank when you keep the application ideal for sometime and click on continue button
Pre Registration
The demographic details are deleted user navigate back to the demographic page
Pre Registration
Getting popup alert when tried to select the dropdown field after filling all the fields
Pre Registration
Unable to view the created application if clicked on Book later or confirmed booking
Pre Registration
URL for Fetch Applicant Type has changed... but not changed in Pre-Registration
Pre Registration
Acceptance Test Rig : Pre-Reg DSL Scenario 4 - pr_updateApplication() missing in the DSL
Pre Registration
Unable to login under pre-registration UI with user already present in Keycloak
Pre Registration
Pre-Reg UI : Screen flicker while scrolling up and down with in any page to see data in Edge browser
Pre Registration
Automation Testing - Able To Get Response Even After Invalidating The Token
Pre Registration
Automation Testing - Trigger Notification Showing Wrong Responses For Invalid Name And Pre Reg ID
Pre Registration
Automation Testing- Trigger Notification Showing wrong response for a request
Pre Registration
Automation Testing - Pre Registration Not Showing any response for wrong request
Pre Registration
Wrong error code returning when the user tries to access another user's demographic data (deleteDocument)
Pre Registration
Status is not updated properly in the dashboard when individual visits the Registration Centre and consumes the appointment.
Pre Registration
Update UIN- Document upload is not mandate though update uin is initiated only for document update.
Resistration client
Unable to continue to registration while clicking on back button after capturing the biometrics.
Resistration client
External Camera provided by Vendor-Syncbyte is not getting detected in a certain scenario
Resistration client
Salt Service Showing Nginx Error while doing the initial sync from reg client
Resistration client
Packet Sync Failure- Invalid Request Value - requesttime (Internal Call from Reg Client to Reg Proc).
Resistration client
OR/SO Onboarding - Biometric screen with Iris selected screen is blank.
Resistration client
Should throw the error pop-up if the child and parent UIN are the same in Update
Resistration client
Should not be continued the Child dob update if Guardian is not selected.
Resistration client
Child Packet with Parent UIN is getting failed at Demographic Verification Stage( unknown exceptions occurred null).
Resistration client
Child packet is getting failed at OSI Stage (Unable to access API resourceRPR-RCT-001 --> Unknown resource provided; nested exception is org.springframework.web.client.HttpClientErrorException: 404 ).
Resistration client
Audit - Reg-client is not sending an audit incorrect format for all registrations
Resistration client
LOST UIN packet is getting failed at the OSI stage (Unable to Find Applicant CBEFF for Adult).
Resistration client
Child/Adult packet is failing in reg proc because of wrong subtype values in the CBEFF file ( Issue is with all types of the packet).
Resistration client
Child Packet is Failed at OSI Stage(Auth System ExceptionRPR-AUT-03 --> Request could not be processed. Please try again).
Resistration client
Capturing bio exception photo or not should not be left to the discretion of the Officer/SO.
Resistration client
"exceptionBiometrics" : [ ] is empty in id.json file, also only face capture is getting stored in packet_meta_info.json
Resistration client
New Registration is displayed in Header when capturing biometrics for UIN Update or Lost UIN.
Resistration client
Onboarding Flow -Capture all biometrics should be mandated If Exceptions are not marked.
Resistration client
schema validation - The uin field should not be mandatory for new registration
Resistration client
New,Update and Lost Flow- Applicant Biometrics screen becomes blank while clicking on the Back button.
Resistration client
Update packet does not contain anything in the id.json(For Ex- UIN and Fields which are selected for update(DOB, EMAIL ETC. )).
Resistration client
Update UIN- Capturing all the biometrics are mandate to proceed further for registrations.
Resistration client
Able to Continue to update UIN without selecting any field for an update.
Resistration client
User has taken to Parents Biometrics screen by clicking on Modify from the Registration Preview screen.
Resistration client
Registration's data is not displayed in registration preview screen /acknowledgement receipt.
Resistration client