Esignet-signup Setup Issue

Support
1

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
image1031×229 20.8 KB

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
  2. The links provided in the esignet-module are invalid: Collab Environment Guides | MOSIP Docs 1.2.0

How can I find the values to add to the application-local.properties.

1 Like
2

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 .

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

keycloak.external.url=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 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 .

You will need iam_url, client_id, and client_secret to generate an auth token.

iam_url = 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