4 shots · about 51 s of finished video · lesson 8 of Documents & certificates
Record as
Principal (demo_principal)
Sign in at /demo on a demo-mode build
Screens
/documents/settings
Length
51 s
narration at ~150 words/min + screen time
Status
Not yet recorded
Before recording
Enter the issuer id and API key from DigiLocker onboarding, map document-type codes, and read the endpoints to register.
| # | Screen | Action (on screen) | Must be visible | Voice-over | ~s |
|---|---|---|---|---|---|
| 1 | /documents/settings | Open Documents → DigiLocker. Callout: Treat this as preparation: the integration is implemented to the public specification but unverified, as the alert says. | Header "DigiLocker issuer — Let students pull their certificates into DigiLocker." and a yellow alert Preparation only: the endpoints follow the published Issuer Pull API shape but have not been tested against DigiLocker. | This page gets the school ready for DigiLocker. The live connection is only possible once DigiLocker has onboarded the school as an issuer. | 13 |
| 2 | /documents/settings | Tick Accept DigiLocker pull requests, enter the Issuer id (orgId) (for example in.gov.wb.schoolname) and the API key ("Shared secret used to verify request HMACs."; once saved the hint shows the last four characters and you can leave it blank to keep it). | The key field is a password field. | These come from DigiLocker onboarding. The API key is a shared secret, so it is masked once saved. | 11 |
| 3 | /documents/settings | Under Document types, map each DigiLocker code to a document type: TCRTC → Transfer certificate, SLCER → School leaving certificate, BNFDC → Bonafide certificate, CHRCT → Character certificate. Use Add code for more (up to 20) and the bin to remove. Click Save settings. | Toast "DigiLocker settings saved". | DigiLocker uses short codes for document types. The mapping tells Unibandh which certificate to return for each code. | 11 |
| 4 | /documents/settings | Copy the Endpoints to register (Pull URI and Pull Doc, both ending in ?school=<your slug>) into the DigiLocker partner portal. The card explains the accepted search keys (SerialNo or AdmissionNo, plus FullName / DOB matching) and the x-digilocker-hmac header. | Two URLs shown in code boxes. | When DigiLocker calls these endpoints with a valid signature, Unibandh looks up the serial or admission number and returns the PDF; the print log records it as a DigiLocker fetch. | 16 |
After the video is published
Add its YouTube id under documents-digilocker in src/lib/help/videos.ts, with a chapters map of step number → seconds. The lesson page then shows the video and a “Watch this step” link on every step. See the video production guide.