Skip to:
Purpose: The PDF version of the certificate is Auto-downloaded after successful authentication to the computer/tablet/smartphone
Pre-requisites:
The JSON response from the Authentication portal should be available to the Inji Web
The user should have already successfully authenticated with the “Authentication Portal”
Basic flow:
The User waits in the same tab as “Authentication Portal” for the PDF to be generated
The user is informed by the “Authentication Portal” (after entering the data) to not “Click Back” button or “ Refresh” the page.
Internal Process at the Inji Web (Not Visible to the user)
The valid JSON response from the “Authentication Portal” is converted into PDF by using the well-known display properties.
The generated PDF is Auto-downloaded to the computer/tablet/smartphone
Or the user is given a prompt pop up message window: suggesting the user to save the PDF document.
The User should be able to open and view the PDF document
The display properties should be coming from the issuer’s well-known
The PDF downloaded should be as per the prototype suggested (UI team to share the prototype)
Key Fields in the PDF certificate
Certificate name
Name of the Holder of the certificate
Name of the institution (if any) issuing this certificate
QR code → Right now it is a dummy QR Code
All other details as defined in the well-known file
Logo of the credential issuer
Business rules: TBA
Acceptance criteria:
The flow as defined above should work seamlessly
The PDF generated should be auto-downloaded after successfully authenticated
Exceptions: No Exceptions
Documentation: Refer here for technical documentation - Yet to be updated
Reference UX: Yet to be updated
Compatibility:
MOSIP: TBA
e-Signet: 1.3.0
Browsers: Google Chrome, Safari, Mozilla Firefox, Microsoft Edge
OS: Windows, MacOS, Android, iOS
Environment:
dev, qa-inji
Story verification is completed on qa-inji env and no critical issues are pending on this story. Hence closing the story
Purpose:
The PDF version of the certificate is Auto-downloaded after successful authentication to the computer/tablet/smartphone
Pre-requisites:
The JSON response from the Authentication portal should be available to the Inji Web
The user should have already successfully authenticated with the “Authentication Portal”
Basic flow:
The User waits in the same tab as “Authentication Portal” for the PDF to be generated
The user is informed by the “Authentication Portal” (after entering the data) to not “Click Back” button or “ Refresh” the page.
Internal Process at the Inji Web (Not Visible to the user)
The valid JSON response from the “Authentication Portal” is converted into PDF by using the well-known display properties.
The generated PDF is Auto-downloaded to the computer/tablet/smartphone
Or the user is given a prompt pop up message window: suggesting the user to save the PDF document.
The User should be able to open and view the PDF document
The display properties should be coming from the issuer’s well-known
The PDF downloaded should be as per the prototype suggested (UI team to share the prototype)
Key Fields in the PDF certificate
Certificate name
Name of the Holder of the certificate
Name of the institution (if any) issuing this certificate
QR code → Right now it is a dummy QR Code
All other details as defined in the well-known file
Logo of the credential issuer
Business rules: TBA
Acceptance criteria:
The flow as defined above should work seamlessly
The PDF generated should be auto-downloaded after successfully authenticated
Exceptions: No Exceptions
Documentation: Refer here for technical documentation - Yet to be updated
Reference UX: Yet to be updated
Compatibility:
MOSIP: TBA
e-Signet: 1.3.0
Browsers: Google Chrome, Safari, Mozilla Firefox, Microsoft Edge
OS: Windows, MacOS, Android, iOS
Environment:
dev, qa-inji