Is Esignet mandatory for Resident Portal?

Developer
, ,
1

Hi guys, I am trying to run the resident portal. Is e-signet really needed, or can Keycloak handle all of that? Also, can the resident portal only be used after the registration client process is complete, or is there any way to use sample data? What should be used for login in the resident portal: VID or UIN? If I try through Keycloak, I can see some available services, but they are just loading since there is no user data, I think. For mock purposes, can we add any data to the DB related to the resident?

2

Hi Tony_Stark!

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

3

Hi @Tony_Stark , thank you for reaching out to us.

I am happy to clarify.

  • The Resident Portal cannot be used independently of eSignet. eSignet is mandatory for authentication.

  • To log in to the Resident Portal in the collab environment, you’ll need a valid Collab Environment UIN.

  • If you don’t already have one, you can generate a UIN by filling out this form. Once the UIN is created, you can use it to access the Resident Portal via eSignet.

  • The Resident Portal is intended to be used after the registration client process, as it relies on resident data generated through registration.

  • Sample or mock data is not supported for Resident Portal usage, and we do not recommend manually inserting resident data into the database, as this can lead to inconsistent behaviour across services.

  • For now, to log into Collab Environment, UIN is the supported identifier (VID support depends on configuration).

If you’re seeing services load via Keycloak but no data appears, that’s expected in the absence of a valid resident record created through the proper flow.

Hope this helps!

Let me know if you need support getting the UIN in Collab environment.

Warm Regards,
Pragya
Product Owner - Resident Portal

4

Hi guys, thanks for the reply. Just a follow-up: If the UIN is created by the registration client, will the resident service be able to pick up this UIN? We are currently using E-Signet with a mock identity system. Does this registration client populate the DB from where the resident service picks up this UIN, and is WebSub needed to do this? Thank you.

5

@Prathmesh_Jadhav Any update on my preceding query?

6

Hi,

Yes — if the UIN is created by the Registration Client, the Resident Services will be able to pick up that UIN.

The Registration Client is responsible for populating the database, and the UIN data finally gets stored in the IDA identity_cache table after passing through the relevant microservices. The complete packet-processing and data flow is clearly illustrated in the following design document:

Regarding module compatibility, the required compatible modules are listed here:

Also, WebSub is required to enable this flow and ensure Resident Services receives the necessary events/data updates.

Thank you.

Regards,
Kamesh Shekhar Prasad
Developer – Resident Portal

7

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