Hi @mrudula_ch
I have moved beyond this point:
I have successfully generated the UIN! I’ve verified this via the Postgres database and Mock-SMTP logs (attached below), where the status for the registration IDs shows as ACTIVATED and the notification emails have been triggered.
Current Status:
-
Database:
mosip_idrepoconfirms UIN generation and activation. -
Reg-Proc:
registration_transactionshowsUIN_GENERATORandFINALIZATIONasSUCCESS. -
Notifications: Mock-SMTP captures the “UIN Generated” emails for the residents.
segun@mosip-wireguardbastionhost1:~$ kubectl exec -n postgres postgres-postgresql-0 – env PGPASSWORD=tkP8ITpNVh psql -U postgres -d mosip_idrepo -c “SELECT uin FROM uin WHERE reg_id=‘34925912752974’;”
uin
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
527_Yu42KPj5vkDb1PiU1MEWgp0CAD5cd32kbmRZmiyArqgKhJFAFCTd_C1tiCRvTCQRPQLAHcJ48dt2I496oSqYN70KcrZZBB_fmoEPpcI8KjrJqmpCQ-tug3ia6xR0qx2vgykxHMvcn4BuY8u9bp1oIS3567X9XwaPcrXE4mGy5veMRCclwQK8zdqa2n8ggouxPcB0Kwe8omUteZHmYMSUGzy3Xz7YZmMeVeVfWjTzUSCXcPswLm8XHLGwiJ96SzEQKcuDXEy-Ega5M9_57UHm3oBG81aiCxNzHoJdvryDp7LISv7-iJXgOQzjA6bUeQokvK8LqL-4JOHh-GF6GYPL4bmoFksJnHr1Pigcoz6uNTDxz7xlqmf9pZiTDmj8_8DLI0tFWV9TUExJVFRFUiN7X5QUXIk3iOFyzfVXavk-qgKDrFT2eQvDaA
(1 row)
segun@mosip-wireguardbastionhost1:~$ kubectl exec -n postgres postgres-postgresql-0 – env PGPASSWORD=tkP8ITpNVh psql -U postgres -d mosip_idrepo -c “SELECT uin FROM uin WHERE reg_id=‘60175829503985’;”
uin
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
127_Yu42KPj5vkDb1PiU1MEWgp0CAD5cd32kbmRZmiyArqg9ocMw6elKi2OmnRrkr9fdjjnH5XzYqsLUNloMU2pCzTsY_FJXK8vF04Vfmqtp9HtW_l2GhJhuqyh0r_XWZMvr6TiIm2aqnOIuAbtveYI9b7znycQBGaEg3cCUfEkJkYyEuF7lDZDM7sAF_qz8Pe2ueQdY21YPz3Rxp_-cXBf2U1u_NOYjhEuA5xjvYUcbbQzHBf9eo3C6EzScKFPBMuhde-8MA6ZPU0eMmlqQInl7hMEr70UppaHnOnss0iMsKVOLtwovJ7B63ZUpOgS5S-QwnP6E7WL3pKVcImTlv3nznPmlX0Io9Xtr4QcFlUKsy0lruHkNpztSuZTvkSM8hCkCI0tFWV9TUExJVFRFUiNu0VVV-Em5-1MMyNhl__yQkg4Bev4Uv5D7Vw
(1 row)
segun@mosip-wireguardbastionhost1:~$ kubectl exec -n postgres postgres-postgresql-0 – env PGPASSWORD=tkP8ITpNVh psql -U postgres -d mosip_idrepo -c “SELECT uin_ref_id, reg_id, status_code, cr_dtimes FROM uin WHERE reg_id=‘34925912752974’;”
uin_ref_id | reg_id | status_code | cr_dtimes
--------------------------------------±---------------±------------±---------------------------
edb3853d-206f-543e-b67b-9bd29e72f307 | 34925912752974 | ACTIVATED | 2026-04-13 16:26:49.589073
(1 row)
segun@mosip-wireguardbastionhost1:~$ kubectl exec -n postgres postgres-postgresql-0 – env PGPASSWORD=tkP8ITpNVh psql -U postgres -d mosip_idrepo -c “SELECT uin_ref_id, reg_id, status_code, cr_dtimes FROM uin WHERE reg_id=‘60175829503985’;”
uin_ref_id | reg_id | status_code | cr_dtimes
--------------------------------------±---------------±------------±---------------------------
6c8c78bb-9530-525e-b8ca-7c31077a7604 | 60175829503985 | ACTIVATED | 2026-04-13 18:42:04.242658
(1 row)
segun@mosip-wireguardbastionhost1:~$ kubectl exec -n postgres postgres-postgresql-0 – env PGPASSWORD=tkP8ITpNVh psql -U postgres -d mosip_regprc -c “SELECT trn_type_code, status_code, status_comment, cr_dtimes FROM registration_transaction WHERE reg_id=‘34925912752974’ ORDER BY cr_dtimes DESC LIMIT 15;”
trn_type_code | status_code | status_comment | cr_dtimes
--------------------------±------------±---------------------------------------------------------------------±---------------------------
INTERNAL_WORKFLOW_ACTION | PROCESSED | Packet processing completed with action code : COMPLETE_AS_PROCESSED | 2026-04-13 16:26:50.705313
PRINT_SERVICE | PROCESSED | Print request submitted | 2026-04-13 16:26:50.555013
FINALIZATION | SUCCESS | idrepo draft was published successfuly | 2026-04-13 16:26:50.032664
BIOMETRIC_EXTRACTION | SUCCESS | biometric extaction was successful | 2026-04-13 16:26:48.800136
UIN_GENERATOR | SUCCESS | UIN Generated Successfully | 2026-04-13 16:26:41.965644
BIOGRAPHIC_VERIFICATION | SUCCESS | Biometric Deduplication is Successful | 2026-04-13 16:26:39.290931
BIOGRAPHIC_VERIFICATION | IN_PROGRESS | Biometric Deduplication In-Progress | 2026-04-13 16:26:34.643394
DEMOGRAPHIC_VERIFICATION | SUCCESS | Demo Dedupe is Successful | 2026-04-13 16:26:34.110873
QUALITY_CLASSIFIER | SUCCESS | Biometric Quality Check is Successful | 2026-04-13 16:26:33.218264
OPERATOR_VALIDATION | SUCCESS | OPERATOR Validation is Successful | 2026-04-13 16:26:31.870045
CMD_VALIDATION | SUCCESS | CMD Validation is Successful | 2026-04-13 16:26:31.565615
PACKET_CLASSIFICATION | SUCCESS | Packet Classification is Successful | 2026-04-13 16:26:30.829301
VALIDATE_PACKET | SUCCESS | Packet Validation is Successful | 2026-04-13 16:26:30.261949
UPLOAD_PACKET | SUCCESS | Packet is Uploaded to Packet Store | 2026-04-13 16:26:26.303012
SECUREZONE_NOTIFICATION | SUCCESS | Notification received to securezone | 2026-04-13 16:26:22.90176
(15 rows)
segun@mosip-wireguardbastionhost1:~$ kubectl exec -n postgres postgres-postgresql-0 – env PGPASSWORD=tkP8ITpNVh psql -U postgres -d mosip_regprc -c “SELECT trn_type_code, status_code, status_comment, cr_dtimes FROM registration_transaction WHERE reg_id=‘60175829503985’ ORDER BY cr_dtimes DESC LIMIT 15;”
trn_type_code | status_code | status_comment | cr_dtimes
--------------------------±------------±---------------------------------------------------------------------±---------------------------
INTERNAL_WORKFLOW_ACTION | PROCESSED | Packet processing completed with action code : COMPLETE_AS_PROCESSED | 2026-04-13 18:42:05.10038
PRINT_SERVICE | PROCESSED | Print request submitted | 2026-04-13 18:42:04.978065
FINALIZATION | SUCCESS | idrepo draft was published successfuly | 2026-04-13 18:42:04.470166
BIOMETRIC_EXTRACTION | SUCCESS | biometric extaction was successful | 2026-04-13 18:42:03.625262
UIN_GENERATOR | SUCCESS | UIN Generated Successfully | 2026-04-13 18:41:57.73261
BIOGRAPHIC_VERIFICATION | SUCCESS | Biometric Deduplication is Successful | 2026-04-13 18:41:54.996503
BIOGRAPHIC_VERIFICATION | IN_PROGRESS | Biometric Deduplication In-Progress | 2026-04-13 18:41:51.109922
DEMOGRAPHIC_VERIFICATION | SUCCESS | Demo Dedupe is Successful | 2026-04-13 18:41:50.517564
QUALITY_CLASSIFIER | SUCCESS | Biometric Quality Check is Successful | 2026-04-13 18:41:49.822696
OPERATOR_VALIDATION | SUCCESS | OPERATOR Validation is Successful | 2026-04-13 18:41:48.349212
CMD_VALIDATION | SUCCESS | CMD Validation is Successful | 2026-04-13 18:41:48.079279
PACKET_CLASSIFICATION | SUCCESS | Packet Classification is Successful | 2026-04-13 18:41:47.112625
VALIDATE_PACKET | SUCCESS | Packet Validation is Successful | 2026-04-13 18:41:46.555943
UPLOAD_PACKET | SUCCESS | Packet is Uploaded to Packet Store | 2026-04-13 18:41:41.949791
SECUREZONE_NOTIFICATION | SUCCESS | Notification received to securezone | 2026-04-13 18:41:38.517
(15 rows)
You can also see the mock-smtp message I got:
--
{ key: 'to', line: 'To: debby@gmail.com' },
{
key: 'message-id',
line: 'Message-ID: <765970451.53.1776097613968@notifier-56968c79d-gfg9q>'
},
{ key: 'subject', line: 'Subject: UIN Generated' },
{ key: 'mime-version', line: 'MIME-Version: 1.0' },
{
key: 'content-type',
line: 'Content-Type: multipart/mixed; \\r\\n' +
'\\tboundary="----=\_Part_51_19751565.1776097613858"'
}
],
html: ‘Dear $name_eng, Your UIN for Registration ID: 34925912752974 has been successfully generated and will reach soon at your postal address. Thank You’,
subject: ‘UIN Generated’,
date: 2026-04-13T16:26:53.000Z,
to: {
value: \[ \[Object\] \],
html: '<span class="mp_address_group"><a href="mailto:debby@gmail.com" class="mp_address_email">debby@gmail.com</a></span>',
text: 'debby@gmail.com'
--
{
type: ‘SMS’,
date: ‘2026-04-13T18:36:15.161Z’,
to: { text: ‘8023068150’ },
from: { text: ‘AD-MOSIP’ },
subject: ‘SMS: Please find the OTP 111111’,
text: ‘Please find the OTP 111111’
}
{
type: ‘SMS’,
date: ‘2026-04-13T18:39:04.098Z’,
to: { text: ‘8023068150’ },
from: { text: ‘AD-MOSIP’ },
subject: ‘SMS: Your Pre-Registration for UIN is Completed Successfully on 13 Apr 2026 at 12:09AM. Your ID is %2360175829503985. Appointment is scheduled for 2026-05-12 at 09:30 AM. you will also receive the details on your registered email address\n’ +
'Votre pré-inscription pour UIN est terminée avec succès sur 13 Apr 2026 à 12:09AM. Votre ID est %23 60175829503985. Le rendez-vous est prévu pour 2026-05-12 à 09:30 AM. vous recevrez également les détails sur votre adresse email enregistrée',
text: ‘Your Pre-Registration for UIN is Completed Successfully on 13 Apr 2026 at 12:09AM. Your ID is %2360175829503985. Appointment is scheduled for 2026-05-12 at 09:30 AM. you will also receive the details on your registered email address\n’ +
'Votre pré-inscription pour UIN est terminée avec succès sur 13 Apr 2026 à 12:09AM. Votre ID est %23 60175829503985. Le rendez-vous est prévu pour 2026-05-12 à 09:30 AM. vous recevrez également les détails sur votre adresse email enregistrée'
}
OK we are done!
{
attachments: [],
headers: Map(7) {
--
line: 'Content-Type: multipart/mixed; \\r\\n' +
'\\tboundary="----=\_Part_54_1736581520.1776105544054"'
}
],
html: ‘Dear Bamikole,\n’ +
'Your $ApplicationDetails application is completed successfully on 13 Apr 2026 at 12:09AM.\\n' +
'Your application id is $ApplicationId.\\n' +
'Appointment is scheduled for 2026-05-12 at 09:30 AM \\n' +
'in Registration Center Center A Ben Mansour at Registration Center Address \\n' +
'P4238 Ben Mansour MyCountry.\\n' +
'\\n' +
--
value: \[Array\],
html: '<span class="mp_address_group"><a href="mailto:bamikole@gmail.com" class="mp_address_email">bamikole@gmail.com</a></span>',
text: 'bamikole@gmail.com'
},
'message-id' => '<663767597.62.1776105727683@notifier-56968c79d-gfg9q>',
'subject' => 'UIN Generated',
'mime-version' => '1.0',
'content-type' => { value: 'multipart/mixed', params: \[Object\] }
},
headerLines: [
{
--
{ key: 'to', line: 'To: bamikole@gmail.com' },
{
key: 'message-id',
line: 'Message-ID: <663767597.62.1776105727683@notifier-56968c79d-gfg9q>'
},
{ key: 'subject', line: 'Subject: UIN Generated' },
{ key: 'mime-version', line: 'MIME-Version: 1.0' },
{
key: 'content-type',
line: 'Content-Type: multipart/mixed; \\r\\n' +
'\\tboundary="----=\_Part_60_506807143.1776105727576"'
}
],
html: ‘Dear $name_eng, Your UIN for Registration ID: 60175829503985 has been successfully generated and will reach soon at your postal address. Thank You’,
subject: ‘UIN Generated’,
date: 2026-04-13T18:42:07.000Z,
to: {
value: \[ \[Object\] \],
html: '<span class="mp_address_group"><a href="mailto:bamikole@gmail.com" class="mp_address_email">bamikole@gmail.com</a></span>',
text: 'bamikole@gmail.com'
The Issue: I am now trying to view the UIN through the Resident Portal. However, whenever I click the “Get My UIN” button, the page fails to load.
Could you provide some insight into why the Resident Portal might not be fetching this data:
And secondly, how do we or where do we get the UIN?
Regards,
John