CODEWITHSUNDEEP
hyperledger-fabricblockchainhyperledger-composer
kumar
kumar

Reputation: 11

Why we should create two connection profiles for one organization, i.e 1. Org1 only and Org1 and Org2 ?

I am using "https://hyperledger.github.io/composer/tutorials/deploy-to-fabric-multi-org" for Deploying Hyperledger Composer blockchain business network to Hyperledger Fabric(mulriple organizations). In this tutorial why we are creating two connection profiles The difference between two connection profiles shown in below image.

Why we should create two connection profiles for onenter image description heree organization, i.e 1. Org1 only and Org1 and Org2 ?

Upvotes: 0

Views: 220

Answers (1)

R Thatcher
R Thatcher

Reputation: 5570

The need for the distinct Org1 and Org2 only cards is related to rights on the Fabric. The initial Runtime Install uses the distinct cards (and connection.json) and subsequent commands - Network Start and Commands from Alice and Bob use cards (and connection profiles) that access all peers regardless of organisation as they have rights to the Network.

For the tutorial (and the Dev Fabric) we have combined the Peer Install role and the Channel admin role into a single identity called PeerAdmin. Then you need an identity to handle the Fabric-ca server issuer role. You also need an identity bound to the initial business network participant. These roles have been combined into one for alice/bob.

Upvotes: 0

Related Questions