# Starting and Configuring Mimoto service - Please guide **URL:** \ **Category:** Developer\ **Tags:** inji\ **Created:** [November 18, 2024, 10:12am UTC](https://community.mosip.io/t/starting-and-configuring-mimoto-service-please-guide/1679 "2024-11-18T10:12:38Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![poonam\_tekdi](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/poonam_tekdi/32/1356_2.png) [@poonam\_tekdi](https://community.mosip.io/u/poonam_tekdi)\ **Post date:** [November 18, 2024, 10:12am UTC](https://community.mosip.io/t/starting-and-configuring-mimoto-service-please-guide/1679/1 "2024-11-18T10:12:38Z")
Hello Team, We wish to import VCs issued from an existing Sunbird RC installation into the wallet and I am setting up the Mimito service locally and following the documentation step by step to run the setup. However, I have the following doubts: Add ID providers as issuers in mimoto-issuers-config.json =\> Who is the ID provider in this case? Start eSignet services and update eSignet host references in mimoto-default.properties and mimoto-issuers-config.json =\> How do I start the eSignet services? oidckeystore.p12 file is attached here. The password to unlock it is xy4gh6swa2i. =\> The documentation mentions: Please find a zip file attached to this document called certgen.zip, which will help in creating the .p12 file as well as the public-key.jwk file. However, I am unable to locate the certgen.zip file. Can you please share the link ---
**Author:** ![swatigoel](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/swatigoel/32/751_2.png) [@swatigoel](https://community.mosip.io/u/swatigoel)\ **Post date:** [November 22, 2024, 8:06am UTC](https://community.mosip.io/t/starting-and-configuring-mimoto-service-please-guide/1679/2 "2024-11-22T08:06:14Z")
Hi @poonam_tekdi Thanks for reaching out to use and sorry for the delay and inconvenience caused. 1. ID provider is nothing but the one which provides data to convert into VC. If you are using certify to pull data from some system or db and then using that VC on mobile or web, then for you it’s certify. But if you have any existing system and integrating Inji with that then this existing system becomes ID provider. 2. Do you want to start esignet locally? or you are looking for esignet running on collab env. 2a. If you are running esignet locally, please go through the session recording once and let us know your challenges. Refer here for resources [Online Hackathon | HackerEarth developer event | MOSIP CREATE](https://www.hackerearth.com/challenges/hackathon/mosip-create/custom-tab/webinar-resources/#webinar-resources) 2b. If you are using esignet running on collab, please refer to this documentation [Credential Providers | Inji](https://docs.inji.io/inji-wallet/inji-mobile/customization-overview/credential_providers#use-mock-data-from-collab-sandbox-env) Easy steps for you, You can refer to this to run mimoto [mimoto/docker-compose at release-0.14.x · mosip/mimoto · GitHub](https://github.com/mosip/mimoto/tree/release-0.14.x/docker-compose) Here is the configuration file [mimoto/docker-compose/config/mimoto-issuers-config.json at release-0.14.x · mosip/mimoto · GitHub](https://github.com/mosip/mimoto/blob/release-0.14.x/docker-compose/config/mimoto-issuers-config.json) You can delete evrything here and have only one issuer as “Mock” which will use esignet from collab env. So your config should look like { “issuers”: [ { “credential\_issuer”: “Mock”, “protocol”: “OpenId4VCI”, “display”: [ { “name”: “Mock Identity”, “logo”: { “url”: “[https://api.collab.mosip.net/inji/mosip-logo.png](https://api.collab.mosip.net/inji/mosip-logo.png)”, “alt\_text”: “mosip-logo” }, “title”: “Mock Identity”, “description”: “Download Mock Identity Credential”, “language”: “en” } ], “client\_id”: “wallet-demo”, “redirect\_uri”: “io.mosip.residentapp.inji://oauthredirect”, “token\_endpoint”: “/v1/mimoto/get-token/Mock”, “authorization\_audience”: “[https://esignet-mock.collab.mosip.net/v1/esignet/oauth/v2/token](https://esignet-mock.collab.mosip.net/v1/esignet/oauth/v2/token)”, “proxy\_token\_endpoint”: “[https://esignet-mock.collab.mosip.net/v1/esignet/oauth/v2/token](https://esignet-mock.collab.mosip.net/v1/esignet/oauth/v2/token)”, “client\_alias”: “wallet-demo-client”, “qr\_code\_type”: “OnlineSharing”, “enabled”: “true”, “wellknown\_endpoint”: “/v1/certify/issuance/.well-known/openid-credential-issuer” } ] } replace this value [mimoto/docker-compose/config/mimoto-default.properties at release-0.14.x · mosip/mimoto · GitHub](https://github.com/mosip/mimoto/blob/release-0.14.x/docker-compose/config/mimoto-default.properties#L263) by `xy4gh6swa2i` looks like, link of p12 file is broken in document, we are fixing it. Please share your email id to share p12 file as p12 file extension is not allowed here. 1. certgen.zip file, we are fixing the linking issue in documentation. Please share your email id to share this as zip file extension is not allowed here. ---
**Author:** ![swatigoel](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/swatigoel/32/751_2.png) [@swatigoel](https://community.mosip.io/u/swatigoel)\ **Post date:** [November 22, 2024, 9:46am UTC](https://community.mosip.io/t/starting-and-configuring-mimoto-service-please-guide/1679/3 "2024-11-22T09:46:35Z")
Hi @poonam_tekdi, Thanks for your patience. There is no need to share your email Id, we have updated our documentation with correct link for p12 and certgen.zip file. Please refer here > **[Credential Providers | Inji](https://docs.mosip.io/inji/inji-wallet/inji-mobile/customization-overview/credential_providers#onboarding-mimoto-as-oidc-client-for-a-new-issuer)**