Collab: Inji Certify issuer missing from Mimoto; PMS has no Partner ID

General
1

I’m testing Inji Wallet with the Collab mock issuer https://injicertify-mock.collab.mosip.net. The live Mimoto issuer list has nine profiles but none for this host. The Wallet reached eSignet, but token exchange returned HTTP 400; the log mentions invalid_redirect_uri, though the cause is unconfirmed.

In PMS, Policies → Request Policy shows “No Data Available” for Partner ID, so I can’t request the eSignet OIDC client. Please advise how to link the correct Authentication Partner ID/policy, add this issuer to the live Mimoto list, and confirm the eSignet client ID, redirect URI, audience, token endpoint, and client authentication settings. The Admin Portal link also won’t load.

2

Hi Sri_Charan_Reddy

Thank you for reaching out to us,Our team will check this and get back to you shortly.

Regards,
Mrudula
on behalf of Team MOSIP

3

@Sri_Charan_Reddy As you rightly pointed we have not configured any issuer in Mimoto to point to mock instance of collab, because we have created mock instance for people to try out things locally.

Mock certify uses mock IDA system so it won’t go through PMS. Mock IDA system is supported by esignet-mock instance. This can be verified through Mock certify well-known https://injicertify-mock.collab.mosip.net/.well-known/openid-credential-issuer Refer `authorization_servers` here.

Now to use Inji certify mock locally to test things, we can follow these steps Credential Providers | Inji

  1. Run mimoto locally by using inji certify from collab as an issuer.
  2. Use client-id, client-alias and p12 file as mentioned in doc
  3. Use UINs mentioned in doc. Those UINs are available in mock IDA system and can be issued as VC through mock certify.

Please let us know if you still face any issue.

Thanks & Regards,
Swati Goel
on behalf of Team INJI

4

Thanks for confirming that shared Collab Mimoto does not include Mock Certify. We’re using the recommended local Mimoto and eSignet Mock IDA route. Our local Mimoto copy is v1.0.0-alpha.1, configured with the root Mock Certify well-known URL and the documented wallet-demo client and alias. Wallet opens on Android 15, but GET http://127.0.0.1:8099/v1/mimoto/issuers times out. Our wallet-only Compose file lists PostgreSQL, Mimoto, and Nginx; Docker Desktop is running, but docker info and docker ps hang. Certify, eSignet, and Verify respond with HTTP 200. What minimum services and startup checks should we use to confirm Mimoto issuer discovery is ready? Is an additional adapter required before the issuer list can respond? No keys, passwords, UINs, tokens, or credential data are included.

5

@Sri_Charan_Reddy For mimoto to provide issuers, we need just mimoto to be up. List of issuers is configured in mimoto and doesn’t rely on any other service.

To get credential issued end to end, we need mimoto, certify, and nginx to run locally. Certify will interact with esignet running on collab env, and certify is accessed through nginx. Then that certify nginx will be configured in mimoto issuer as credential issuer host.

To access services on Mobile app, we need to expose docker service on https through any tunnel like ngrox, cloudflare.