Deployment issue about esignet

1

Hello MOSIP Team,

I am currently deploying esignet locally using the Kubernetes-based installation method. Following the documentation in

, I have successfully deployed eSignet 1.6.1 inside the same MOSIP cluster(I already deployed a MOSIP cluster locally) and executed the onboarding process. The onboarding job completed without any visible errors (screenshot attached).

image
image595Ă—306 4.49 KB

However, when I log into the Resident Portal and click UIN Services, the page redirects to eSignet but shows the following error:

“Client ID is invalid. Please try again.”

image
image1886Ă—949 33.6 KB

After checking the code, it appears that this Client ID is read by the Resident backend from its configuration file.

At this point, I am unsure how I should correctly configure the Client ID for Resident → eSignet integration. Is there any guidance or documentation on how these values should be mapped or registered during eSignet onboarding?

Could you please advise how to resolve this issue or direct me to the appropriate documentation?

Thank U

UPDATE

As a follow-up to my previous question, I have continued investigating the integration between Resident Portal and eSignet. After reviewing multiple documents, I believe the next step might be to create a client for the Resident Portal via the OIDC API.

In the eSignet deployment repository, I noticed the postman-collection folder, which contains APIs that appear to be used for registering clients. However, I still have several questions regarding the parameters required by the API:

{
  "id": "string",
  "version": "string",
  "requesttime": "{{$isoTimestamp}}",
  "metadata": {},
  "request": {
    "name": "{{$randomCompanyName}}",
    "policyId": "93482",
    "publicKey": {{client_public_key}},
    "authPartnerId": "{{relying_party_id}}",
    "logoUri": "{{$randomImageUrl}}",
    "redirectUris": [
      "{{redirection_url}}"
    ],
    "grantTypes": [
      "authorization_code"
    ],
    "clientAuthMethods": [
      "private_key_jwt"
    ]
  }
}

Could you please clarify the following?

  1. What should be used for policyId, publicKey, authPartnerId, and redirectUris?
  2. Should I create a new Authentication Policy for this client in the Partner Management Portal (PMP)?
  3. The documentation mentions generating a key pair for the client. Where should the private key be stored? Should it be placed inside the Resident Service?
  4. What exactly does authPartnerId refer to? Since Resident Portal is not listed as an authentication partner, should it be registered as one?
  5. For redirectUris, should it be the base URL of the Resident Portal or a specific callback endpoint?

Any clarification or guidance on these points would be greatly appreciated.

2

Hi there!

Thanks for reaching out.
We are looking into your query/feedback and will get back to you soon!
Until then, happy coding with MOSIP!

Best regards,
Team MOSIP

1 Like
3

Hello ryan

Are you able to see the OIDC client ID added as a secret in his resident namespace in the setup?
Does an “invalid client ID” mean that the client ID is not present?
Also, are you able to check his eSignet database to verify whether the value is present there?

4

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.