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.
8 custom credential schema(s) from http://verifiably-go:8080/api/registry-credentials. Sunbird: http://156.67.105.185:18091
FreshDelegV1 entity registered
Issuer: — · Standard: freshdelegv1_vc_ldp
Sunbird entity: FreshDelegV1
Fields: onBehalfOfroleallowedActionvalid_untilstatusUristatusIdxstatusType
FreshDelegV2 entity registered
Issuer: — · Standard: freshdelegv2_vc_ldp
Sunbird entity: FreshDelegV2
Fields: onBehalfOfroleallowedActionvalid_until
FreshSubjectV1 entity registered
Issuer: — · Standard: freshsubjectv1_vc_ldp
Sunbird entity: FreshSubjectV1
Fields: subjectRefgivenName
FreshSubjectV2 entity registered
Issuer: — · Standard: freshsubjectv2_vc_ldp
Sunbird entity: FreshSubjectV2
Fields: subjectRefgivenName
Testa Auth Inji Del V1 entity registered
Issuer: — · Standard: testaauthinjidelv1_vc_ldp
Sunbird entity: TestaAuthInjiDelV1
Fields: onBehalfOfrole
Testa Auth Inji V1 entity registered
Issuer: — · Standard: testaauthinjiv1_vc_ldp
Sunbird entity: TestaAuthInjiV1
Fields: last_nametesta_id
Testa Auth Inji W3C Del V8 entity registered
Issuer: — · Standard: testaauthinjiw3cdelv8_vc_ldp
Sunbird entity: TestaAuthInjiW3CDelV8
Fields: onBehalfOfroleallowedActionvalid_until
Testa Auth Inji W3C V8 entity registered
Issuer: — · Standard: testaauthinjiw3cv8_vc_ldp
Sunbird entity: TestaAuthInjiW3CV8
Fields: testa_idlast_name