# Esignet-signup Setup Issue **URL:** \ **Category:** Support\ **Tags:** esignet\ **Created:** [August 28, 2025, 4:31pm UTC](https://community.mosip.io/t/esignet-signup-setup-issue/2276 "2025-08-28T16:31:32Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Lakshya\_Kapoor](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/lakshya_kapoor/32/1714_2.png) [@Lakshya\_Kapoor](https://community.mosip.io/u/Lakshya_Kapoor)\ **Post date:** [August 28, 2025, 4:31pm UTC](https://community.mosip.io/t/esignet-signup-setup-issue/2276/1 "2025-08-28T16:31:32Z")
I’m trying to setup my development environment to contribute to the esignet-signup repository for the MOSIP Hackathon. I’m following the docker-compose README. I can’t find out the valid values to add here. ![image](https://europe1.discourse-cdn.com/flex017/uploads/mosip1/original/2X/0/06d714f7cee7d45d41cadbb546c76e11470acb31.png) In the AMA session I was directed to access the collab environment for this. But the documentation is lacking details in certain areas: 1. The prerequisites for setting up MOCK SMTP doesn’t provide a link: [Collab Environment Guides | MOSIP Docs 1.2.0](https://docs.mosip.io/1.2.0/general/collab-getting-started-guide#pre-requisites) 2. The links provided in the esignet-module are invalid: [Collab Environment Guides | MOSIP Docs 1.2.0](https://docs.mosip.io/1.2.0/general/collab-getting-started-guide#esignet-simple-and-secure-online-authentication) How can I find the values to add to the application-local.properties. ---
**Author:** ![zesu2210](https://avatars.discourse-cdn.com/v4/letter/z/ad7895/32.png) [@zesu2210](https://community.mosip.io/u/zesu2210)\ **Post date:** [September 1, 2025, 7:50am UTC](https://community.mosip.io/t/esignet-signup-setup-issue/2276/2 "2025-09-01T07:50:25Z")
Hi @Lakshya_Kapoor **Running E-Signet in a Local Environment** This guide provides a step-by-step process for running the E-Signet application locally. While the existing documentation may have some issues, this workflow has been verified to be functional. **Step 1: Clone and Configure the E-Signet Signup Repository** Clone the esignet-signup repository. Navigate to the docker-compose folder and open the dependent-docker-compose.yml file. Add the following property to the E-Signet environment: `MOSIP_ESIGNET_SIGNUP_ID_TOKEN_AUDIENCE=mosip-signup-oauth-client` (Note: `mosip-signup-oauth-client` is the client ID for the signup application. You can use any ID here, but ensure it is the same ID you use when creating the signup client.) Run this Docker Compose file after making the modification. **Step 2: Configure the E-Signet Core** Refer to the E-Signet documentation at [esignet/docker-compose at master · mosip/esignet · GitHub](https://github.com/mosip/esignet/tree/master/docker-compose) . Follow the instructions for steps 4, 5, and 6. Step 7 is for the relying party, which you can customize as needed. Execute the instructions for step 8. To complete these steps, you will need Postman and the Postman collection provided in the E-Signet Docker Compose documentation. Upon completing these steps, you should have successfully created both an E-Signet client and a mock identity. **Step 3: Configuration for running esignet-signup** Return to the esignet-signup/docker-compose documentation. Make the following changes in application-local.properties: Properties > mosip.internal.domain.url=[https://api-internal.collab.mosip.net](https://api-internal.collab.mosip.net) > > keycloak.external.url=[https://iam.collab.mosip.net](https://iam.collab.mosip.net) > > mosip.signup.client.secret=p6lNpTHOd7X3VTwNPeCEbKf4Boyqje7X > > // Point to the file created by the shell script. > > mosip.signup.oauth.keystore-path=../../oidckeystore.p12 Follow points 4 through 6 to verify that your flow is working correctly. **Step 4: Configure the E-Signet Signup Client** Navigate to the esignet-signup documentation at [esignet-signup/README.md at master · mosip/esignet-signup · GitHub](https://github.com/mosip/esignet-signup/blob/master/README.md#partner-onboarding) to create a signup client. Import the Postman collection and its environment file (available in the cloned repository) into the Postman application. Follow the OIDC client management instructions at [esignet-signup/README.md at master · mosip/esignet-signup · GitHub](https://github.com/mosip/esignet-signup/blob/master/README.md#oidc-client-management-instructions) . You will need `iam_url`, `client_id`, and `client_secret` to generate an auth token. > iam\_url = [https://iam.collab.mosip.net](https://iam.collab.mosip.net) > > client\_id = mosip-decode-signup-client > > client\_secret = p6lNpTHOd7X3VTwNPeCEbKf4Boyqje7X After generating the token, follow step 3 to properly create the signup client. Also you need to run signup-ui as well, it is a react application which you can run with npm start. If you encounter any issues, please feel free to ask for assistance. Thanks and Regards Zeeshan ---
**Author:** ![Lakshya\_Kapoor](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/lakshya_kapoor/32/1714_2.png) [@Lakshya\_Kapoor](https://community.mosip.io/u/Lakshya_Kapoor)\ **Post date:** [September 9, 2025, 7:13pm UTC](https://community.mosip.io/t/esignet-signup-setup-issue/2276/3 "2025-09-09T19:13:53Z")
Thanks a lot for the detailed guide. I’ve followed all the steps mentioned and I want to clarify certain ambiguities to verify if my setup is correct. - step 3 point 5 which plugin jar should be used (mock-plugin/identity-plugin)? - After running signup-ui I’m getting the following error toast “your network connection dropped, please check your internet connection.“ even though there is no issue with my network. Attaching screenshots for the same: ![Screenshot](https://europe1.discourse-cdn.com/flex017/uploads/mosip1/original/2X/1/1683c83418c75a241fd642e434fa142d653ad01b.png) What should I do to fix this? ---
**Author:** ![zesu2210](https://avatars.discourse-cdn.com/v4/letter/z/ad7895/32.png) [@zesu2210](https://community.mosip.io/u/zesu2210)\ **Post date:** [September 11, 2025, 9:15am UTC](https://community.mosip.io/t/esignet-signup-setup-issue/2276/4 "2025-09-11T09:15:01Z")
hi @Lakshya_Kapoor , You should use `mock-plugin`, when you are running locally. Your main starting point should be the `esignet` flow, not the signup-ui page. The `signup-ui` is a basic page with options for `registration` and `password reset`, but you can ignore it for your primary task. When you’re authorizing through esignet, if a necessary verified claim is missing, the system will automatically redirect you to the `identity-verification` page. It’s important to know that you can’t open the identity-verification page directly in your browser; it will only appear after being redirected from the esignet authorization process. Thanks & Regards Zeeshan ---
**Author:** ![Jayesh\_Pandit](https://dub1.discourse-cdn.com/flex017/user_avatar/community.mosip.io/jayesh_pandit/32/1706_2.png) [@Jayesh\_Pandit](https://community.mosip.io/u/Jayesh_Pandit)\ **Post date:** [September 12, 2025, 7:21pm UTC](https://community.mosip.io/t/esignet-signup-setup-issue/2276/5 "2025-09-12T19:21:37Z")
![image](https://europe1.discourse-cdn.com/flex017/uploads/mosip1/original/2X/2/2e96ce0630614b9c2249d0af47a154a57a1dff5d.png) We are facing issues completing the setup and need guidance on the next steps. So far, we have: - Run the Docker containers and JAR files as per the README - Created the OIDC client and navigated to the authorization URL We are unclear on what details to provide for verification, where to receive the OTP, which UIN ID is required, and why we cannot access the health services site. Can you please direct us how to proceed further with the local setup or have a small zoom session to explain the next steps. Thank you for your support. ---
**Author:** ![system](https://europe1.discourse-cdn.com/flex017/uploads/mosip1/original/1X/f60a343830fe848c9a68e2d1cc654d0cb7fbbaf2.svg) [@system](https://community.mosip.io/u/system)\ **Post date:** [September 22, 2025, 7:22pm UTC](https://community.mosip.io/t/esignet-signup-setup-issue/2276/6 "2025-09-22T19:22:36Z")
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.