Need Guidance on Local Integration Workflow for Inji Wallet, eSignet, and Inji Certify

1

Hello MOSIP Community,

I am currently trying to integrate Inji Wallet, eSignet, and Inji Certify in my local environment. However, I am facing some issues due to my limited understanding of the overall integration workflow.

While verifying the logs, I noticed that the following API appears to be causing the issue:

http://localhost:8088/v1/esignet/oauth/authorize

I would really appreciate your guidance on the following:

  1. The end-to-end local integration workflow for Inji Wallet, eSignet, and Inji Certify

  2. A brief explanation of the role and responsibility of the major APIs/services involved

  3. Any common configuration steps or troubleshooting points I should verify for this authorization flow

If there is any existing documentation, setup guide, or reference architecture for running these components together locally, please do share it.

Thank you in advance for your support.

2

Hello Tayyab_Sirkazi

Thank you for reaching out. We will look into the issue you mentioned and get back to you shortly.

Regards,

Mrudula
on behalf of Team MOSIP

3

thank you @mrudula_ch

4

@Tayyab_Sirkazi can you share esignet logs?

To start esignet locally, have you followed the esignet local setup?

5

good afternoon swati thanks a lot for responding,
i referred the video available in official mosip channel in youtube.

please find the logs attached below. it contains both esignet and mimoto logs

6

Hi @Tayyab_Sirkazi

It appears you are running eSignet locally. Can you confirm whether a client ID has been created for your local setup?

The logs indicate wallet-demo as the client_id, which is typically the default when using eSignet from the collab environment. Please confirm on this..

Please follow these steps to create client_id Credential Providers | Inji

Regards

Likhitha R L

on behalf of team INJI