Details
-
Task
-
Status: Closed
-
Medium
-
Resolution: Done
-
None
-
None
Description
On one hand, here we would need to refactor the code associated to membership service functionalities, i.e., code for signing w.r.t. a certificate, certificate signature verification to export the interface agreed within FAB-829. This would substitute the default membership service provider for fabric.
Another task associated to this story is that throughout the implementation of this default IDP we would need to make sure that crypto calls go through our BC-CSP that was implemented in FAB-355.
Attachments
Issue Links
- relates to
-
FAB-1986 Ability to use an existing (commercial) CA
-
- Closed
-
-
FABN-734 Implement BCCSP importKey()
-
- Closed
-
-
FAB-355 As an infrastructure developer and application developer i want to have availale a software based crypto provider implementing the interface of FAB-354 in golang.
-
- Closed
-
-
FAB-354 As an infrastructure developer I want to specify a crypto API, that can satisfy all the crypto needs of existing & future peer and membership services
-
- Closed
-