Deploying esignet containers

1

Hello MoSIP team,

We’re currently facing an issue while using the provided eSignet service for developers during testing.

We’ve deployed the eSignet containers on a VPS server as part of our app prototyping. However, it appears that the eSignet server expects the token URL to always be localhost, and does not accept any other IP address or hostname. While everything works fine in our local development environment, we consistently receive an “invalid assertion” error when running it on the VPS.

Is there a recommended way to configure or override this behavior to support non-localhost URLs? Any guidance would be greatly appreciated.

Thank You

2

Dear @inno_waluza ,

Thank you for reaching out and explaining the issue you are facing, One of our expert colleagues will respond here with solution input.

Best Regards
Team MOSIP

1 Like
3

HI @inno_waluza

Kindly check the below property value

  1. mosip.esignet.token.endpoint
  2. mosip.esignet.discovery.issuer-id

Make sure the values are set as per your eSignet domain name.

If eSignet helm charts are used for the deployment, then the values.yaml should set up the environment with the correct values.

Note:
This is the line that decides the “aud” value in the client assertion

regards,
MOSIP Team

1 Like
4

okay Anusha I’ll come back to you,|
thanks