Kunstmaan / Kunstmaan/hyperledger-fabric-node-chaincode-utils
What would happen if a user certificate is revoked?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 21
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
We are using txHelper.getPublicKey function in our token example, but what would happen if a certificate is revoked and the user will not be able to use this certificate in the network anymore.
We may need an additional mechanism using stub.getBinding(), getTransient() inside a transaction in which the invoker can pass an additional cert/public key or a message signed with his private key. This private key would be with the user and this can be independent from the fabric network, we can use this public key to identify the user rather than using his cert provided by the MSP of any organization as this can be revoked anytime.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the token example that uses txHelper.getPublicKey, then review the proposed stub.getBinding() and getTransient() transaction APIs. Determine how certificate revocation should affect identity and what fallback signature or public-key behavior is expected; the issue is complete only when that mechanism and its security requirements are agreed and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- authentication, blockchain, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100