title: HyperLedger Fabric v1.1 adding organizations to existing channels
body: <p>Following is given as part of hyperldedger fabric documentation for v1.1:</p>
  
  <p>Switching between organizations to sign a config transaction (or to do anything else) is not reflective of a real-world Fabric operation. A single container would never be mounted with an entire network’s crypto material. Rather, the config update would need to be securely passed out-of-band to an Org2 Admin for inspection and approval.</p>
  
  <p>Say we have 4 organizations Org1,Org2,Org3 and Org4 and we are in the process of creating Org5.</p>
  
  <p>Let Org1 and Org2 belong to same cli whereas Org3 be in Org3cli and Org4 be in Org4cli</p>
  
  <p>Let us say all initial steps to launch org5 into network has been done.</p>
  
  <p>On coming to peer channel signconfigtx I first sign from cli using peers of Org1 and Org2.But I need one more signature as majority says 3.</p>
  
  <p>I go to Org3cli as sign on behalf of org3 but since peer channel signconfigtx method is local cli (Containing Org1 and Org2) doesn't come to know about it.(result is not send to the orderer).</p>
  
  <p>So given in a real world scenario that a single cli isn't expected to handle all configuration,How do u handle interaction between 2 different cli ?</p>