- Idrepo will publish a websub event when an identity is created or updated to IDENTITY_CHANGED topic. This event will contain the registration Id / application Id responsible for the change, UIN salted hash and the event sub type (created / updated).
- PDFCard service will subscribe to this IDENTITY_CHANGED topic and will receive the event. Then a request to credential request generator with this RID and credential type as VC is sent.
- RID with the UIN salted hash received in the event and the request id received from the credential request generator response is stored in the database.
- Credential request generator service will store the request in its database and the batch job will forward the request to credential service
- Credentail service will create a encrypted verifiable credentail based on the configured policy for the RID and will store it in datashare service
- The datashare URL return from datashare service along with the request id is then published as a websub event to the PDF Card service specific topic in websub
- Websub will deliver the event to the PDF card service
- PDF card service will use the datashare URL to download the encrypted verifiable credential, will decrypt the same and verify
- PDF card service will use the verifiable credentail to create the password protected PDF file based on configured PDF template and will upload the same to datashare service without partner encryption. This template will mostly match the print template used by the country. The password used for pdf protection will be year of birth of the applicant.
- The datashare PDF file URL received through upload is then saved into the DB for the same request id and RID
- The PDF file URL along with request id and status as STORED is published as a websub event to the CREDENTIAL_STATUS_UPDATE topic
- Websub delivers the event to the credential request generator service and the status with datashare URL is updated to the database.
- Applicant will login to the resident UI, navigate to PDF card download page and will request for OTP using the "Generate OTP for RID" API of resident service
- Resident service will call the idrepo idvid API to get the UIN of the RID, if RID is not found in idrepo then resident service will return to resident UI to try after few days message
- If UIN is found, resident service will send request to IDA internal auth service to generate OTP for the UIN and respond to resident UI that OTP is generated successfully
- Applicant once receiving the OTP, will provide the same in resident UI and the request with RID and OTP will be sent to the resident service to download the PDF card.
- Resident service will call the idrepo idvid API to get the UIN of the RID
- The internal auth request will be formed using the UIN and the OTP and will be sent to IDA for validation
- Once authentication is succesful, request with RID will be sent to PDFCard service to retrieve the datashare URL of the PDF card file
- PDFCard service will hash search in database to find the datashare URL to the requested RID. But this step is optional if the datashare URL can be formed using the RID and other details without connecting to database which can help with performance improvement.
- Request will be sent to datashare service to download the PDF card file
- The PDF file will be streamed back to the resident UI to complete the flow
- Admin will login to the Admin UI, navigate to PDF card download page and will provide the RID in the page for admin UI to send request to "GET Applicant Verfication details" API of admin service
- Admin service will call the idrepo idvid API to get the date of birth and photograph of the applicant linked to the RID
- If RID is valid and if details are available, admin service will respond to the Admin UI with the same details for admin user to manually verify the applicant
- Once the manual verification is success, admin will acknowledge the verification and will click on download PDF button. Admin UI will send request to the download PDF API with RID
- Request with RID will be sent to PDF card service to retrieve the datashare URL of the PDF card file
- PDFCard service will hash search in database to find the datashare URL to the requested RID. But this step is optional if the datashare URL can be formed using the RID and other details without connecting to database which can help with performance improvement.
- Request will be sent to datashare service to download the PDF card file
- The PDF file will be streamed back to the admin UI to complete the flow