MOSIP-41019: Upon providing invalid request time, getting 500 error, instead of invalid requesttimestamp

[Ivanmeneges]

auth_EkycOtp_Auth_With_Invalid_Empty_Timestamp_UIN_Neg

Request body:

{
"request": "agCt9SvU_Wz8yQwmbOYRmjQT3ThqWcO16ZqC_8BsWZdNixHQ7116EqFIpveEYf1JSV6tza773aZjCIpjgIRE12ztucqytd-bf5TpZSk7CyY1rKK0eeo2",
"specVersion": "1.0",
"thumbprint": "CA105F804B08444DBC9A3259E9628025AF95B887EC153C41BD7C92A81ECF9D76",
"individualId": "4760520871",
"env": "Staging",
"version": "1.0",
"transactionID": "9946943444",
"domainUri": "[https://api-internal.released.mosip.net",](https://api-internal.released.mosip.net](https://api-internal.released.mosip.net)",)
"requestHMAC": "7Yz4Fr26o3d5Q9WZivexxf3t-ipZsUUWROtS2fWB2VJ6Nk8zn7L3XlAEEv735OoJMVfyg6OxeDE3QfzBhw3dZAo6xjvo62zZHMZRu-fROQP0NCVHbeNfGlrwJ0YYUGZS",
"requestTime": "2dhdh.809Z",
"requestedAuth": {
"pin": false,
"bio": false,
"otp": true,
"demo": false
},
"keyIndex": "string",
"consentObtained": true,
"id": "mosip.identity.kyc",
"individualIdType": "UIN",
"requestSessionKey": "bj9LQDArzMsc7sdZlJvOxF6qqW_f9EVKDlXPqgoQzKmMEnurQ3DevPhAjp0TnsAAzqGWHNbW75qYNUbA_baALCGlUZL729YhlyN0I4pLuBcyKXmqTPb4pB7vMPBT9T4GFUd2zUg-KwIpU7_nFeNsZHJK_irHTsGmQvk_IR_rqQnuRJb_dwots0aQJq0UGCylWwd7Tu1vUmXTIhMDyYz1A3pDXLBkB478Kp2EEAK8jewC-XGwL5nxxRAOVXyfEniza-CBkEL1FurjHXx7SpMVfSW1j_Is1NttSWJ6pOCDoR2syh4klsj7i7Po-L-n3O7ckVjh6B6HcvoBpT4LcaBLQg\u003d\u003d"
}

Response body:

{
"timestamp": "2025-03-25T06:00:29.708+00:00",
"status": 500,
"error": "Internal Server Error",
"message": "IDA-IDV-001 --\u003e Input Data Validation Failed; \nnested exception is io.mosip.authentication.core.exception.IDDataValidationException",
"path": "/idauthentication/v1/kyc/2siLc4GvpDuFsO6OjdewFWicWqY3rsdDT8UN1q9E7FvzkdnNGJ/auth_ekyc_pid1742880323256/29951"
}

Expected Output: Should get valid error message

Attaching the report for the reference:

mosip-api-internal.released-auth-2025-03-25_05-26-full-report_T-603_P-577_S-1_F-20_I-5_KI-0.html

🔗 Linked Issues

ISSUE

• MOSIP-41856
  Status: Closed
• MOSIP-37285
  Status: Closed
• MOSIP-37285
  Status: Closed
• MOSIP-41856
  Status: Closed

📎 Attachments

• ida-auth-6bf54d6989-t7fxs_ida-auth.log

• mosip-api-internal.qa1-java21-auth-2025-09-22_09-22-full-report_T-620_P-587_S-1_F-27_I-5_KI-0.html

• mosip-api-internal.qaga-auth-2025-12-05_08-30-full-report_T-612_P-598_S-0_F-1_I-5_KI-8.html

• mosip-api-internal.released-auth-2025-03-25_05-26-full-report_T-603_P-577_S-1_F-20_I-5_KI-0.html

[Ivanmeneges]

varaniya commented: [~accountid:712020:aadfe03f-47db-45df-83f0-889d2229ac9e] this is to be marked as known issue only for the release 1.2.1.0-beta.1 (Part 4), since this needed more effort to debug

[~accountid:5a507d8482ad5d29a77684d7] this needed to be fixed before the next release

Cc: [~accountid:5c18fe9f16ac1e4f7cbb5d3a]

[Ivanmeneges]

Md Tarique Azeez commented: [~accountid:63295ec9f568615bdc7ad1a4] the issue has been fixed. Could you please test the scenario now?
code is merged in develop branch.

[Ivanmeneges]

Anuranjan Kumar commented: Re-tested in qa1-java21 with develop branch but still failing. Hence re-opening.

[^ida-auth-6bf54d6989-t7fxs_ida-auth.log]
[^mosip-api-internal.qa1-java21-auth-2025-09-22_09-22-full-report_T-620_P-587_S-1_F-27_I-5_KI-0.html]

[Ivanmeneges]

Sradha Mohanty commented: Linked the related ticket that confirms this issue has been fixed. The issue has been removed from the known issues list.

[Ivanmeneges]

Mohanachandran S commented: Assigning to [~accountid:636a272c11c69c7418450dbe] for verification

[Ivanmeneges]

swetha.N commented: Issue still exists. Hence reopening the bug, verfiied in qaga.mosipnet

Attached the report for refernce

[^mosip-api-internal.qaga-auth-2025-12-05_08-30-full-report_T-612_P-598_S-0_F-1_I-5_KI-8.html]