Hello Community, I'm working on a use case where I need to use certificates, which bind resources to identities, that have been already issued by an Authoritative CA with the Fabric Network I'm develo

#signcerts #interoperability #fabric-ca #x509

Hi Nik, You are right! Defining the policy using the MSP ID's of the organizations, everything works as expected. Thank You. Stefano

#policies #fabric-chaincode #fabric-questions #fabric-endorser

Hi Community, Still facing the same issue. Additional log from monitordocker.sh net_test: "peer0.org2.example.com|2021-03-29 12:22:25.948 UTC [discovery] chaincodeQuery -> ERRO 066 Failed constructing

#policies #fabric-chaincode #fabric-questions #fabric-endorser

Hi Nik, Thanks for answering. I confirm the chaincode has been committed to the channel: peer lifecycle chaincode commit -o localhost:7050 --ordererTLSHostnameOverride orderer.example.com --peerAddres

#policies #fabric-chaincode #fabric-questions #fabric-endorser

Using the default configuration I can run all the functions inside the application folder of commercial paper on test-network without any problem If I edit the default signature policy in the approval

#policies #fabric-chaincode #fabric-questions #fabric-endorser