Thoubles with mimoto service

Developer
1

Dear Mosip team,

I am writing to report a recurring issue I am encountering with the mimoto service when attempting to issue a credential. The process fails immediately after the e-signature step, despite using a valid UIN(UIN = 5860356276).

The mimoto service is receiving a HTTP 400 Bad Request error when calling the certify service’s credential issuance API. The error response indicates a problem fetching data from the database.

I suspect this is related to a database access or data parametrization issue within the certify service, possibly the NullPointerException we observed in the previous logs when the data provider plugin was invoked.

Description of the Issue

I am having trouble with the mimoto service. When I attempt to issue a credential (specifically, calling the /v1/mimoto/credentials/download endpoint), I get the following error just after e-signing. I am using a valid UIN.

The key error is that the mimoto service received a 400 Bad Request error from the certify service with the specific payload: {"error":"ERROR_FETCHING_DATA_RECORD_FROM_TABLE","error_description":"ERROR_FETCHING_DATA_RECORD_FROM_TABLE"}.

Local Service Logs (mimoto service)

Here are the logs of the local service:

2025-10-15 12:18:14 {"@timestamp":"2025-10-15T15:18:14.269Z","@version":"1","message":"RestApiClient::postApi()::error uri: http://certify-nginx:80/v1/certify/issuance/credential 400 : \"{\"error\":\"ERROR_FETCHING_DATA_RECORD_FROM_TABLE\",\"error_description\":\"ERROR_FETCHING_DATA_RECORD_FROM_TABLE\"}\"

Request for Assistance

Could you please analyze these logs and provide guidance on how to resolve the ERROR_FETCHING_DATA_RECORD_FROM_TABLE issue? I suspect the root cause lies within the certify service’s data fetching logic. I would also appreciate assistance regarding the recurring OIDC connection error.

Thank you for your time and assistance.

2

Hello @mmorenoragni

Thank you for reaching out.

If you are trying this using the Docker Compose setup, please recheck the UIN in the CSV file located in the config folder.
The error you’re encountering occurs because the system is unable to locate the UIN in the data source (either the CSV or the PostgreSQL database). Please try it out and let us know if issue still persist.

Regards

Likhitha R L

on behalf of Team MOSIP

3

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.