Mimoto pod is not comming up with the 0.17.0 version

Inji
1

Hello Team,

While accessing injiweb ui , when we click on get started, it is saying service currently unavailable… deployed the latest mimoto that is 0.17.0 as the current version v0.15.2 is failing to fetch the list of issuers, but after deploying 0.17.0 the pod is throwing error like ‘Validation failed in Mimoto-issuers-config.json:’ even after i have updated the Mimoto-issuers-config.json from the latest config branch 0.7.0
the 0.15.2 pod is coming up without an issue… only 0.17.0 pod is having problem.

getting below errors in mimoto logs
Validation failed in Mimoto-issuers-config.json:
Errors for issuer at index: 1 with issuerId - Mosip

  • credential_issuer_host must be a valid URL
  • proxy_token_endpoint must be a valid URL
  • wellknown_endpoint must be a valid URL
    Errors for issuer at index: 2 with issuerId - StayProtected
  • credential_issuer_host must be a valid URL
  • proxy_token_endpoint must be a valid URL
  • wellknown_endpoint must be a valid URL
    Errors for issuer at index: 3 with issuerId - Mock
  • credential_issuer_host must be a valid URL
  • proxy_token_endpoint must be a valid URL
  • wellknown_endpoint must be a valid URL
    Errors for issuer at index: 4 with issuerId - MosipTAN
  • proxy_token_endpoint must be a valid URL
    Errors for issuer at index: 5 with issuerId - Land
  • credential_issuer_host must be a valid URL
  • proxy_token_endpoint must be a valid URL
  • wellknown_endpoint must be a valid URL

currently these below versions are running in our env:
inji-web = mosipid/inji-web:0.12.0
inji-verify = mosipid/inji-verify:0.10.0
inji-certify = mosipid/inji-certify:0.10.2
mimoto = mosipid/mimoto:0.17.0
esignet = mosipid/esignet:1.4.1
datashare = mosipid/data-share-service:1.3.0-beta.2

Please let us know if we are missing anything.

2

Hi Gagana.A,

Thank you for the detailed update.

The validation you’re encountering has been fixed as part of Mimoto v0.17.0. In earlier versions (like v0.15.2), these validations were not enforced, which is likely why the issues in the mimoto-issuers-config.json file went unnoticed.

Now that the validations are active, the config file must comply strictly with the expected schema — in particular, fields like credential_issuer_host, proxy_token_endpoint, and wellknown_endpoint must contain valid URLs for each issuer.

Please review and correct the mentioned fields in your mimoto-issuers-config.json file as per the errors shown in the logs. If the file already seems correct and the issue persists, feel free to share the config file with us, and we can help debug it further.

Let us know how it goes.

Best regards,
Gurpreet Kaur

3

Hi Gurpreet,

Mimoto-issuers-config.json from the latest config branch only i.e, 0.7.0 , it containes all the fields, still getting same error as i updated above.

4

@Gagana.A Quick question — are the placeholders ${mosip.injicertify.mosipid.host}, ${mosip.api.public.host}, and ${mosipid.identity.esignet.host} getting resolved at runtime?

The provided JSON input will fail validation if placeholders appear to be unresolved.