Certificate Lifecycle Management

[ChakshuGautam]

What are RC's views on Certificate Lifecycle?

1. Issuance - Should RC allow the issuance of credentials for entities (Issuer and Subject) not part of the Registry? If yes, how is this currently implemented?
2. Storage - Should it allow credentials created by an external authority to be imported in RC? If yes, how? How does verification work in this case?
3. Verification - What are RC's views on the verification of credentials generated outside of RC? If yes to 2 how should this be done?
4. Sharing - Is there an opinion on how credentials should be shared? I saw the two implementations - PDF (and by extension an HTML page), and QrCode. There are other implementations as well that allow for importing and sharing of credentials.

Example Use Cases

1. Credential data is not stored by a central authority and is being stored in a transactional data store distributed across departments.
2. Credential creation and revocation will be managed by the departments and not by RC.
3. Need to enable private partners and people outside of the registry (or part of some other registry not compliant with RC) to generate their own credentials that can be imported to the user's wallet.

Specific Priority Use Cases

1. Credential transfer between wallets (at scale): - Ramesh, studying in grade 11 in a government school recently received an academic achievement credential in his state education wallet. However, Ramesh wants to transfer this academic achievement credential to his DigiLocker account.

2. Pulling in credentials from different sources (for the pilot): - Suraj, studying in grade 5 wants to apply online for a scholarship that is being provided to students from the EWS category. He wants to pull his EWS status certificate from another department onto his state edu wallet so that he can apply for the scholarship directly by sharing the digital records of his current school enrolment and his EWS status certificate.