| layout | |||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
g2p_openid_vci_programs
G2P OpenID VCI: Programs
- This module adds a new issuer type called
Beneficiary,extending the G2P OpenID VCI module functionality. It effectively adds the ability to issue VC for beneficiaries who are part of a program in PBMS. - It adds a parameter to attach a Program to an Issuer. With this module, each Program in PBMS is an issuer.
- For example, if three programs are operating on PBMS, 3 different issuers can be created with issuer_type as "Beneficiary" and different programs.
- Configure 3 different scopes for the three issuers. Example:
- IssuerName: "SafetyNetIssuer", scope: "safety_net_program_vc_ldp", Program: "Safety Net Program".
- IssuerName: "HumAidIssuer", scope: "hum_aid_program_vc_ldp", Program: "Humanitarian Aid Program", etc.
- If the content of the credential is the same for all the 3 programs, then use a generic credential_type and format across all three issuers, like "OpenG2PBeneficiaryVerifiableCredential". If the content is different in all programs, use different credential types.
- Configure 3 different scopes for the three issuers. Example:
- For example, if three programs are operating on PBMS, 3 different issuers can be created with issuer_type as "Beneficiary" and different programs.
- Unlike a Registry VC, a Beneficiary may contain additional data, like the name of the Program, the duration for which this beneficiary is part of the program, the last date till which this beneficiary is part of the program, etc. This module supports all of these.
Note:
- A credential will only be issued if the sub from auth JWT exists as one of the IDs in the registry against a registry entry, and the registrant is also an enrolled beneficiary of the said program.
- The rest of the functionality from the base module remains the same.