Handling Case Insensitive Duplicated User Details
Last updated
Last updated
Copyright © 2021 MOSIP. This work is licensed under a Creative Commons Attribution (CC-BY-4.0) International License unless otherwise noted.
In the registration processor, there was an issue where packets were failing at the supervisor validation stage when the username of the supervisor was entered in a different case than it appeared in the database. To resolve this issue, a case insensitive search will be implemented to retrieve the username of the supervisor during the validation stage.
In order for this fix to work properly, it is necessary for the user_id
column of the user_details
table in the master database to not contain any case insensitive duplicates.
If there are any duplicates in this table, packets will fail at the supervisor validation stage once again. Therefore, it is important to deactivate or delete these case insensitive duplicates. It should be noted that this action will not have any impact on other areas, as the mapping between keycloak users and the user_id
of the user_details
table is one-to-one and case insensitive.
user_id
column of the user_details
table?Follow these steps:
Log in to the master schema of the mosip_master
database.
Open a query tool.
Execute the following SQL command in the query tool:
Make sure to copy the output to a text file to manage the duplicate data effectively.
Login in to the admin portal with a user having ZONAL_ADMIN
role.
On the left pane, click on Resources
in the side-menu.
Select User Center Mapping
under Resources in the side-menu.
Click Filter on the User Center Mapping
page.
Enter the user_id
that was retrieved from the database and copied into the text file. After entering the user_id
, click on the Apply button.
Now, on the User Center Mapping
page, case insensitive duplicates of user_id
would be displayed.
Based on the Center, choose the entry that can be deactivated/deleted.
Now click on the ellipsis of the selected entry.
Select the appropriate action (Delete/ Deactivate) on that entry.