Registry Admin — the data-source tier for verifiably’s Inji credential flow
Issuers define credentials in verifiably; here you populate the authoritative registry (Sunbird RC) those credentials draw from. When a holder signs up via eSignet and claims a credential, verifiably auto-pulls their data from this registry by their Individual ID and issues it into the credential. One Sunbird entity per credential type — enter records keyed by Individual ID, or bulk-import CSV.
10 custom credential schema(s) from http://verifiably-go:8080/api/registry-credentials. Sunbird: http://156.67.105.185:18091
Alumni Card entity registered
Issuer: — · Standard: alumnicard_vc_ldp
Sunbird entity: AlumniCard
Fields: alumniIdgradYear
Farmer Land Credential entity registered
Issuer: — · Standard: farmer_land_vc_ldp
Sunbird entity: FarmerLandCredential
Fields: holderNameparcelIdareaHectaresvillagetenureType
Health Pass entity registered
Issuer: — · Standard: healthpass_vc_ldp
Sunbird entity: HealthPass
Fields: patientIdvaccine
Library Card entity registered
Issuer: — · Standard: librarycard_vc_ldp
Sunbird entity: LibraryCard
Fields: memberIdmemberNameexpiryDate
RegistryDemoCard entity registered
Issuer: — · Standard: registrydemocard_vc_ldp
Sunbird entity: RegistryDemoCard
Fields: programcohort
Testa Card V2 entity registered
Issuer: — · Standard: testacardv2_vc_ldp
Sunbird entity: TestaCardV2
Fields: last_nametesta_id
Testa Card V3 entity registered
Issuer: — · Standard: testacardv3_vc_ldp
Sunbird entity: TestaCardV3
Fields: first_nametesta_id
Testa Card V5 entity registered
Issuer: — · Standard: testacardv5_vc_ldp
Sunbird entity: TestaCardV5
Fields: last_nametesta_id
Testa Credential V1 entity registered
Issuer: — · Standard: testacredentialv1_vc_ldp
Sunbird entity: TestaCredentialV1
Fields: last_namereg_id
Verifiable Person Credential entity registered
Issuer: — · Standard: mock_identity_vc_ldp
Sunbird entity: VerifiablePersonCredential
Fields: fullNamegivenNamefamilyNamegenderdateOfBirthemailphoneNumber