1. posterid:949103
  2. funtionality for msp in different folders

Re: funtionality for msp in different folders

meng <qsmeng@...>
 

Hi Baohua,
  In my view, it would be better to rename the four msp in the four folders as follows:
  ca: the ca as the org's trust root, which sign the enroll cert for org's member, indeed provide memebership service for its members;
 msp: should be org's identity or membership, used to sign on behalf of the org;
msp in peers: should be peer's identity or membership, used to sign on behalf of the peers;
msp in users: should be user(client)'s identity or membership, used to sign on behalf of the users;

Thanks.
best regards,
Meng


At 2017-06-08 21:48:03, "Baohua Yang" <yangbaohua@...> wrote:
Hi meng

It's a hierarchical structure. And the most important part is the msp folder under each (sub)structure:

  • ca: the ca as the trust root
  • msp: msp files of the org
  • peers: sub structures for those peer nodes
  • users: sub structures for those users


And for each msp, you may see:

  • admincerts: cert for the administrator role
  • cacerts: certs for the trusted ca
  • keystore: private keys for signing
  • signcerts: public cert for signing verification (for identity).

Hope this can help u.

Thanks!



On Thu, Jun 8, 2017 at 4:49 PM, meng <qsmeng@...> wrote:
Hi all,
   Following the getting started document, I get the crypto-config.  In org1.example.com under the peerorganizations, there are four folders: ca, msp, peers,users.  I want to know the respective functionalities  for this msp and the one in the peers folder respectively.
  Thank you.
 best regards,
Meng


 


_______________________________________________
Hyperledger-fabric mailing list
Hyperledger-fabric@lists.hyperledger.org
https://lists.hyperledger.org/mailman/listinfo/hyperledger-fabric




--
Best wishes!

Baohua Yang


 
Join {fabric@lists.hyperledger.org to automatically receive all group messages.