-
Notifications
You must be signed in to change notification settings - Fork 8.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fabric Gateway not taking intermediate certificate into account #3224
Comments
These are the logs from my peer:
|
@afrancoc2000 the fix has been merged |
Fix backported to release-2.4 for inclusion in v2.4.3. |
Hi @afrancoc2000, before we release v2.4.3, could you confirm whether this fix works for you, please? Thanks! |
Hi @andrew-coleman although I'm not getting the "certificate signed by unknown authority" error, the client still doesn't work, I'm getting now an error on the orderer telling me that the client didn't provide a tls certificate. These are the logs in the client:
These are the logs in the peer:
These are the logs in the orderer:
I double checked and I do have a client certificate set on the grpc connection:
I guess the problem now is not with the ca certificates but still it doesn't work. Thanks |
Ok, this looks like a separate problem. Currently the gateway does not support mutual TLS between the gateway server and other peers and orderer nodes: This will need to be implemented. I'll raise a separate issue for this. |
Ok, thanks |
@afrancoc2000, the mutual TLS issue has been fixed and merged (#3234). Please could you let me know if this resolves the problem you were seeing? Thanks! |
@andrew-coleman with your last fix things started working! thanks! |
Do not work for fabric 2.5. docker exec -t cli.peer0.${ORG}.${DOMAIN} peer lifecycle chaincode commit --channelID common --name ${chaincodeName} --version 1.0 --sequence 2 --init-required --tls --tlsRootCertFiles $ORDERER_CA --peerAddresses peer0.${ORG}.${DOMAIN}:7051
|
thanks! |
Is there a solution for 2.5? |
@paweldzielak @epewerner This issue describes a bug in the peer Gateway service implementation, preventing the Gateway service connecting to other nodes when intermediate TLS certificates are used. This has been fixed. You seem to be describing a similar bug in the |
Hi,
I'm having trouble making the "Hyperledger Fabric Gateway for Go" execute a smart contract, although I am using it successfully for listening to events.
This is the error I get in the client:
This is the error I get in the orderer:
This is the error I get in the peer:
The IP 10.250.37.195 corresponds to the ingress service external IP and the 10.250.37.115 corresponds to the ingress controller. The ingress controller has ssl-passtrough configured so the certificates are not being overridden by it.
I'm using a chain certificate that begins with an ica cert and then on the same file the root certificate, this chain.crt file is stored in the orderers in this folder: "/var/hyperledger/orderer/tls/chain.crt" both ORDERER_GENERAL_TLS_ROOTCAS and ORDERER_GENERAL_TLS_CLIENTROOTCAS point to it.
I tested my tls certificate against the chain.crt using openssl and the answer is ok.
I tested my code against the test network and it works, also using the old node SDK the connection works too.
This is my code (deleting err handling for readability):
I tried also overiding the pod's ssl certificates by adding the ca certificates to /usr/local/share/ca-certificates/ and using the update-ca-certificates command with no luck.
I posted a question in the hyperledger chat in here and thanks to the help of @yacovm we found that the intermediate CA certificate is not being taken into acount as can be seen here
Adding the intermediate certificate should fix the problem.
Thanks
The text was updated successfully, but these errors were encountered: