This is a general repository where change requests (as Issues) can be placed for consideration. The P&A group, through the Triage process, will determine which OCI artifact is impacted and, if approved, will assign the Issue to a Repo or create a project and create sub-issues and assign each of them to Repos.
0
stars
0
forks
source link
Approach to Credential Revocation (hold until Q2, 2024) #8
Steering summary:
As part of OCI's continuous improvement, we suggest to introduce a new credential revocation method. This would affect wallet providers and credential issuers to modify their current set-ups. It should be considered whether the current method shall be replaced or whether OCI will support 2 revocation methods. Supporting more than 1 method will require wallets to implement 2 methods, which may be seen as a barrier to entry. In case of a complete switch to the new method, credentials connected to the current method would need to be reissued to be compatible with the new method. Thus, transition mgt would also need to be considered.
the P&A chairs would like to draw your attention to the proposal of switching from the current LDAP-based credential revocation method to an Ethereum-based one.
Steering summary: As part of OCI's continuous improvement, we suggest to introduce a new credential revocation method. This would affect wallet providers and credential issuers to modify their current set-ups. It should be considered whether the current method shall be replaced or whether OCI will support 2 revocation methods. Supporting more than 1 method will require wallets to implement 2 methods, which may be seen as a barrier to entry. In case of a complete switch to the new method, credentials connected to the current method would need to be reissued to be compatible with the new method. Thus, transition mgt would also need to be considered.
the P&A chairs would like to draw your attention to the proposal of switching from the current LDAP-based credential revocation method to an Ethereum-based one.
LDAP is mentioned in the following conformance criteria. Main sections: wallet: https://open-credentialing-initiative.github.io/Digital-Wallet-Conformance-Criteria/latest/#credential-revocation issuer: https://open-credentialing-initiative.github.io/Credential-Issuer-Conformance-Criteria/#credential-revocation Plus several smaller mentions in the wallet criteria.
Here is some background information in preparation of our discussion. Spherity's LDAP assessment (see below) Spherity's Medium article re Ethereum method: https://medium.com/spherity/how-issuers-can-manage-credential-revocation-19b2f573054f Spherity's GitHub: https://github.com/spherity/ethr-revocation-registry
affected artifacts: