Fabric CA sample fails with TLS error when
running against latest 1.1 code because orderer
was expecting client certificate but was not receiving
on during TLS handshake. This change set fixes the
problem by specifying --clientauth, --keyfile and
--certfile command line arguments to the peer commands
that need to communicate with orderer, like 'peer channel
create'.
Change-Id: I34ad39c919c0121916116c3711c7429009db7fc8
Signed-off-by: Anil Ambati <aambati@us.ibm.com>
This change set makes bootstrap peers aligned to recommended
settings.
Change-Id: Ibd29577000d1a91d091c595ac3f32c00cead1d13
Signed-off-by: yacovm <yacovm@il.ibm.com>
org3 peer role is not enabled in org3-artifacts/org3-crypto.yaml
which causes failure in executing the transaction on org3.
adding the following configuration fixes the issue
"EnableNodeOUs: true"
Change-Id: Id345583a7f5a1f8fb970c8e6113a094de82b6358
Signed-off-by: ratnakar <asara.ratnakar@gmail.com>
This change-set does the following:
- it modifies the first-network example to show how to use FAB-5664.
Namely, the identity classification is enabled by
setting EnableNodeOUs to true in crypto-config.yaml.
Then, the endorsement policy is changed to requires
peers and not members. Finally, cryptotx.yaml is modified
to enable v1.1 capabilities.
Change-Id: If8e943b5833b4402d612895449ac110ab2fee4b5
Signed-off-by: Angelo De Caro <adc@zurich.ibm.com>
The fabric-samples/fabric-ca/scripts/setup-fabric.sh script needs
two small changes so that orderers and peers are registered with
the correct type. They are currently defaulting to type 'client'.
Change-Id: Ibd813cd68ae1669bc39423826ca1d39ac57d16c1
Signed-off-by: luomin <luomin_tokyotech@hotmail.com>
This change brings a new set of scripts and configuration files to the
first-network sample to make it easier for people to follow the new
tutorial on how to add a third org to the network setup in BYFN.
To function properly the new Extend You First Network script (eyfn.sh)
must be run after byfn.sh is run and with the same parameters. So,
valid uses include:
./byfn.sh up
./eyfn.sh up
or
./byfn.sh up -c testchannel -s couchdb -l node
./eyfn.sh up -c testchannel -s couchdb -l node
A single './eyfn.sh down' command is however necessary to take the
whole network down.
Patch-set #2: fixes ./eyfn.sh down
Patch-set #3: removed unused option from Usage and spurious whitespaces
Patch-set #4: added missing test file
Change-Id: I9c926b52f2243dda1c5f9368112c314a6c5c6929
Signed-off-by: Arnaud J Le Hors <lehors@us.ibm.com>
Currently client authentication is not enabled on
any peers and orderer in the fabric-ca sample. This
change set will enable client authentication on all
the peers and orderer.
Change-Id: If3c6a5dc6d1dc3a38096608617971945bde359c0
Signed-off-by: Anil Ambati <aambati@us.ibm.com>
Fix the instructions in chain-docker-devmode for v1.1-perview.
Resubmit this FAB-6934 due to the merge conflict.
https://gerrit.hyperledger.org/r/#/c/15405/
Change-Id: I6d2dece3f48ca8b8c904c0745adb2253a7c6581a
Signed-off-by: luomin <luomin_tokyotech@hotmail.com>
The stop.sh script cleans up the network and service
containers from the composition file, but does not
clean up the resulting chaincode containers. This
CR removes the chaincode containers and their images
as well.
Change-Id: I06ba13486efc59b4761728891aab27535ae0366d
Signed-off-by: Latitia M Haskins <latitia.haskins@gmail.com>
Recently, Fabric CA was changed to restrict custom attributes
from starting with "hf." prefix. But fabric-ca sample was
using hf.admin custom attribute. Hence it was failing. This
change set changes custom attribute "hf.admin" to "admin".
Change-Id: I6c9324e62717c26aab3c2d308d9fb098ecd2fb65
Signed-off-by: Anil Ambati <aambati@us.ibm.com>
Add sample couchdb index to marbles02 chaincode
to support the chaincode queries.
Also update the go chaincode instructions with
index instructions, and fix the examples to
indicate that chaincodeid should not be included
in queries or indexes as of 1.1.
Change-Id: I4a3b0dbeb83c6a2cf40c73fcee5aed20427acfca
Signed-off-by: David Enyeart <enyeart@us.ibm.com>
Fix the following error:
[[{"code":0,"message":"No identity type provided. Please provide identity type"}]]
Change-Id: I5a0b04aadbf87d1661f9605f0eb4ec9b2dbab62a
Signed-off-by: Abdul Rauf <abdulraufmujahid@gmail.com>
Fix the chaincode location by adding "go" subdirectory to path.
Change-Id: Idc72a0f4fcecf519d49a68d141025ada054cf847
Signed-off-by: Keith Smith <bksmith@us.ibm.com>
Trivial fix of a typo which causes the app to
crash
Change-Id: I55bb6a0e971d21adb0bd50f450571d6698686c9a
Signed-off-by: Gari Singh <gari.r.singh@gmail.com>
The admin identity needs hf.Registrar.Roles attribute so
it can register other identities. This attribute was
introduced recently in fabric-ca v1.1.0-alpha.
Change-Id: Ie2a0ef705f07a35580c6bc8a85a34b9b9d937623
Signed-off-by: Anil Ambati <aambati@us.ibm.com>
According to this tutorial http://hyperledger-fabric.readthedocs.io/en/latest/write_first_app.html
the function name is spelled changeCarOwner.
Renamed changeCarowner to changeCarOwner.
Change-Id: Ic32c76137e3686cbf951f846da0ef8c4c5d8986d
Signed-off-by: Nikita Klein <objcoding@gmail.com>
This change fixes a set of related issues.
It fixes the use of the cli timeout setting. It is now merely about
the maximum time spent waiting for a response.
The e2e script is no longer run from docker-compose but by calling
docker exec from byfn.sh and docker-compose now merely has the cli
waiting/sleeping for 1000 seconds.
This not only allows starting the network without automatically
running the e2e script, it also allows byfn.sh to properly end when
the e2e script ends rather than hang. It also makes the tutorial
simpler.
The time the cli container waits/sleeps cannot be changed other than
by editing the config file but this shouldn't be a problem.
This change also fixes the log output of the e2e script so that peers
are consistantly being referenced as in peerX.orgY.
In addition, this changes the usage of byfn.sh so that the -m
parameter is no longer needed. One merely needs to type "./byfn.sh up"
rather than "./byfn.sh -m up". The old way is still supported though,
for human backward compatibility. ;-) And by default the answer to the
prompt for continuation is "y" so the user can simply continue with a
hit of the return key.
Change-Id: I3e2409d81018f97ec9306ce6e1ae916d8fe18fec
Signed-off-by: Arnaud J Le Hors <lehors@us.ibm.com>
Crypto materal is cleared after every re-start of a new network
Change-Id: I01c919109401428de1252695930f42e73eb3f795
Signed-off-by: ratnakar <asara.ratnakar@gmail.com>
This CR replaces the expired certificates with the msp library
in fabric/sampleconfig.
Regenerate the orderer.block and myc.tx artifact using the
configtx.yaml in fabric/sampleconfig. Profiles used are
SampleSingleMSPSolo & SampleSingleMSPChannel. Modify the
orderer profile in configtxyaml and change address from
127.0.0.1:7050 -> orderer:7050 before reading in the file
to configtxgen. This allows the peer to
resolve with the ordering service when the docker compose
is spun up.
Change CORE_PEER_ADDRESS from 7051 to 7052 when starting
the chaincode in dev mode.
Change-Id: I0dbd3f81553c85943a4219123f086e69081c4f5a
Signed-off-by: Nick Gaski <ngaski@us.ibm.com>
This is a sample application that demonstrates usage of Fabric SDK typings.
Change-Id: I5b9b42c666de51a490043cafe0faac29e4f4a0a4
Signed-off-by: Kapil Sachdeva <ksachdeva17@gmail.com>
The CLI timeout for byfn is currently set to
10000 seconds. This is not a huge issue, but
does mean that the CLI will hang around for
10000 seconds after the e2e is complete.
This simply changes the default timeout to
10 seconds.
Change-Id: I4e163ed248d9e937354e83c0d0143dc6748b6a08
Signed-off-by: Gari Singh <gari.r.singh@gmail.com>
The balance transfer sample commands do not work.
Fixed the readme sample commands along with a few
supporting application code.
Change-Id: I74c5ff150f26e4c1868201499eb616daca316ee8
Signed-off-by: Bret Harrison <beharrison@nc.rr.com>
Steps include: revoking a user, generating a CRL,
updating the CRL in the configuration block of the
channel, and finally querying the chaincode using
the revoked user credentials. The query will fail as
it is invoked by a revoked user.
Change-Id: I3b0f26d9b5a78475b6f42543b0e17458e9ce2a73
Signed-off-by: Anil Ambati <aambati@us.ibm.com>
"queryChaincode" doesn’t output responses from all
peers in log message. It exits the loop processing after
outputting the first response.
We should print all responses from all peers. Also, we should
return a response (e.g. the response_payloads[0]) after the loop.
This patch fixes the problems above.
Change-Id: I92a0c5a663d6da0854d89bf76c5ba36da86754ef
Signed-off-by: Yuki Kondo <yuki.kondo@hal.hitachi.com>
This CR adds two new yaml files that are specific to a new
organization - Org3 - that will join the existing application
channel. Also adds a separate docker-compose that is specific
to the new org - Org3.
Update byfn.sh to remove the Org3 artifacts
Reliant on CR - 15323
Change-Id: I22a08be6f8472f981c4231491b7cae56906b71dd
Signed-off-by: Nick Gaski <ngaski@us.ibm.com>
Maybe this sub-task is too stricky and tiny.
To make the source easier to be read together as explained in the WYFA doc.
Change-Id: Icc0dc56c3e25ca7b8d4828935addd5ec7229e51c
Signed-off-by: Min Luo <luomin_tokyotech@hotmail.com>
When a CA starts, it creates its signing cert and then
starts listening on its listening port. The fix is to
wait for the server to start listening on the port rather
than waiting for the signing cert file to be created.
See the waitPort function in env.sh, and places where this
is called. I also had to increase the max time we wait before
failing.
WARNING: This change set is dependent upon the following
fabric-ca change set and should not be merged until it
has been merged:
https://gerrit.hyperledger.org/r/#/c/15089/
Change-Id: I781e3653bf6846e22f401fe64855fa155ffeb7cb
Signed-off-by: Keith Smith <bksmith@us.ibm.com>
Chaincode mount path has been corrected with this fix so
that artifacts (ex. mychannel.block etc.,) won't be visible on
the host machine and the cli container upon restart.
Change-Id: I9b59c80d1cac3034d9cd7d9e19b2931df8b3988e
Signed-off-by: ratnakar <asara.ratnakar@gmail.com>
It's possible to run byfn -m generate multiple
times depending on how you go through the
tutorials, start/stop the network, etc.
The crypto-config folder is deleted when
running byfn -m down and that will stay,
but now each time generateCerts is run the
cyrpto-config folder will be deleted as well.
Change-Id: Ie3851debd76ff0c50c84e14fbca56de2a28bd825
Signed-off-by: Gari Singh <gari.r.singh@gmail.com>
fabcar uses 1.0.2 node modules changing it to unstable so that
latest node modules can be used on master branch
Change-Id: Ia9dc866931763760dd3cd7dbc5c7fd9a5de099be
Signed-off-by: ratnakar <asara.ratnakar@gmail.com>
