title: Hyperledger Fabric: signing channel update
body: <p>I am using Hyperledger Fabric v2.2 with multiple organizations setup. I want to join a new organization to an existing channel. The problem is in signing channel update.</p>
  <p><a href="https://hyperledger-fabric.readthedocs.io/en/release-2.2/config_update.html#get-the-necessary-signatures" rel="nofollow noreferrer">Fabric docs</a> says that there are two main implementations of signing:</p>
  <ol>
  <li>“pass it along” - admin of <code>Org1</code> signs channel update and sends in to <code>Org2</code> admin, <code>Org2</code> admin signs and sends to <code>Org3</code> and so on, until enough signatures will be collected.</li>
  <li>&quot;The other option is to submit the update to every Admin on a channel and wait for enough signatures to come back. These signatures can then be stitched together and submitted. This makes life a bit more difficult for the Admin who created the config update (forcing them to deal with a file per signer) but is the recommended workflow for users which are developing Fabric management applications.&quot;</li>
  </ol>
  <p>All samples that I found describes only the first implementation. But how to do it with the second? I found the related code in <a href="https://hyperledger.github.io/fabric-sdk-node/release-1.4/tutorial-channel-create.html" rel="nofollow noreferrer">HLF Node.js SDK v1.4</a> but can't find the same for v2.2.</p>