-
Notifications
You must be signed in to change notification settings - Fork 89
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
Warning : The identity is a member of a different MSP #349
Closed
Comments
denyeart
added a commit
to denyeart/fabric
that referenced
this issue
Dec 13, 2021
PR hyperledger#3006 added warnings for principal check failures to assist with troubleshooting. The discovery warning was too much however since even in normal scenarios discovery endorser service checks the peer against the various channel principals. This change reverts to the prior code without the warning. Resolves hyperledger/fabric-gateway#349. Signed-off-by: David Enyeart <enyeart@us.ibm.com>
ale-linux
pushed a commit
to hyperledger/fabric
that referenced
this issue
Dec 13, 2021
PR #3006 added warnings for principal check failures to assist with troubleshooting. The discovery warning was too much however since even in normal scenarios discovery endorser service checks the peer against the various channel principals. This change reverts to the prior code without the warning. Resolves hyperledger/fabric-gateway#349. Signed-off-by: David Enyeart <enyeart@us.ibm.com>
mergify bot
pushed a commit
to hyperledger/fabric
that referenced
this issue
Dec 13, 2021
PR #3006 added warnings for principal check failures to assist with troubleshooting. The discovery warning was too much however since even in normal scenarios discovery endorser service checks the peer against the various channel principals. This change reverts to the prior code without the warning. Resolves hyperledger/fabric-gateway#349. Signed-off-by: David Enyeart <enyeart@us.ibm.com> (cherry picked from commit 0b0c35c)
denyeart
added a commit
to hyperledger/fabric
that referenced
this issue
Dec 13, 2021
PR #3006 added warnings for principal check failures to assist with troubleshooting. The discovery warning was too much however since even in normal scenarios discovery endorser service checks the peer against the various channel principals. This change reverts to the prior code without the warning. Resolves hyperledger/fabric-gateway#349. Signed-off-by: David Enyeart <enyeart@us.ibm.com> (cherry picked from commit 0b0c35c)
Fixed in Fabric v2.4.1. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Network setup:
Started a 3 orgs 2 peers each.
Created the channel and deployed chaincode
gateway peer:peer.org1.example.com
Issue:
Logs are getting populated with warning messages while making successful transactions:
[discovery.acl] SatisfiesPrincipal -> identity does not satisfy principal error="the identity is a member of a different MSP (expected Org1MSP, got Org2MSP)" errorVerbose="the identity is a member of a different MSP (expected Org1MSP, got Org2MSP)\ngithub.mirror.nvdadr.com/hyperledger/fabric/msp.(*bccspmsp).satisfiesPrincipalInternalV142\n\t/go/src/github.com/hyperledger/fabric/msp/mspimpl.go:628\ngithub.mirror.nvdadr.com/hyperledger/fabric/msp.(*bccspmsp).SatisfiesPrincipal\n\t/go/src/github.com/hyperledger/fabric/msp/mspimpl.go:430\ngithub.mirror.nvdadr.com/hyperledger/fabric/msp/cache.(*cachedMSP).SatisfiesPrincipal\n\t/go/src/github.com/hyperledger/fabric/msp/cache/cache.go:123\ngithub.mirror.nvdadr.com/hyperledger/fabric/msp/cache.(*cachedIdentity).SatisfiesPrincipal\n\t/go/src/github.com/hyperledger/fabric/msp/cache/cache.go:58\ngithub.mirror.nvdadr.com/hyperledger/fabric/common/cauthdsl.compile.func2\n\t/go/src/github.com/hyperledger/fabric/common/cauthdsl/cauthdsl.go:77\ngithub.mirror.nvdadr.com/hyperledger/fabric/common/cauthdsl.compile.func1\n\t/go/src/github.com/hyperledger/fabric/common/cauthdsl/cauthdsl.go:47\ngithub.mirror.nvdadr.com/hyperledger/fabric/common/cauthdsl.(*policy).EvaluateIdentities\n\t/go/src/github.com/hyperledger/fabric/common/cauthdsl/policy.go:103\ngithub.mirror.nvdadr.com/hyperledger/fabric/common/cauthdsl.(*policy).EvaluateSignedData\n\t/go/src/github.com/hyperledger/fabric/common/cauthdsl/policy.go:93\ngithub.mirror.nvdadr.com/hyperledger/fabric/common/policies.(*PolicyLogger).EvaluateSignedData\n\t/go/src/github.com/hyperledger/fabric/common/policies/policy.go:286\ngithub.mirror.nvdadr.com/hyperledger/fabric/common/policies.(*ImplicitMetaPolicy).EvaluateSignedData\n\t/go/src/github.com/hyperledger/fabric/common/policies/implicitmeta.go:92\ngithub.mirror.nvdadr.com/hyperledger/fabric/common/policies.(*PolicyLogger).EvaluateSignedData\n\t/go/src/github.com/hyperledger/fabric/common/policies/policy.go:286\ngithub.mirror.nvdadr.com/hyperledger/fabric/internal/peer/gossip.(*MSPMessageCryptoService).VerifyByChannel\n\t/go/src/github.com/hyperledger/fabric/internal/peer/gossip/mcs.go:246\ngithub.mirror.nvdadr.com/hyperledger/fabric/internal/peer/gossip.(*MSPMessageCryptoService).Verify\n\t/go/src/github.com/hyperledger/fabric/internal/peer/gossip/mcs.go:222\ngithub.mirror.nvdadr.com/hyperledger/fabric/gossip/identity.(*identityMapperImpl).Verify\n\t/go/src/github.com/hyperledger/fabric/gossip/identity/identity.go:179\ngithub.mirror.nvdadr.com/hyperledger/fabric/gossip/gossip.(*Node).validateStateInfoMsg.func1\n\t/go/src/github.com/hyperledger/fabric/gossip/gossip/gossip_impl.go:1230\ngithub.mirror.nvdadr.com/hyperledger/fabric/gossip/protoext.(*SignedGossipMessage).Verify\n\t/go/src/github.com/hyperledger/fabric/gossip/protoext/signing.go:132\ngithub.mirror.nvdadr.com/hyperledger/fabric/gossip/gossip.(*Node).validateStateInfoMsg\n\t/go/src/github.com/hyperledger/fabric/gossip/gossip/gossip_impl.go:1236\ngithub.mirror.nvdadr.com/hyperledger/fabric/gossip/gossip.(*gossipAdapterImpl).ValidateStateInfoMessage\n\t/go/src/github.com/hyperledger/fabric/gossip/gossip/chanstate.go:180\ngithub.mirror.nvdadr.com/hyperledger/fabric/gossip/gossip/channel.(*gossipChannel).handleStateInfSnapshot\n\t/go/src/github.com/hyperledger/fabric/gossip/gossip/channel/channel.go:786\ngithub.mirror.nvdadr.com/hyperledger/fabric/gossip/gossip/channel.(*gossipChannel).HandleMessage\n\t/go/src/github.com/hyperledger/fabric/gossip/gossip/channel/channel.go:628\ngithub.mirror.nvdadr.com/hyperledger/fabric/gossip/gossip.(*Node).handleMessage\n\t/go/src/github.com/hyperledger/fabric/gossip/gossip/gossip_impl.go:372\ngithub.mirror.nvdadr.com/hyperledger/fabric/gossip/gossip.(*Node).acceptMessages\n\t/go/src/github.com/hyperledger/fabric/gossip/gossip/gossip_impl.go:326\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1371" requiredPrincipal="principal:\"\\n\\007Org1MSP\\020\\003\" " identity="(mspid=Org2MSP subject=CN=peer0.org2.example.com,OU=peer,L=San Francisco,ST=California,C=US issuer=CN=ca.org2.example.com,O=org2.example.com,L=San Francisco,ST=California,C=US serialnumber=280541228011480321420417454954707362033)"
peer0.gateway.log
The text was updated successfully, but these errors were encountered: