Yes, that’s one common approach we’ve seen. The EDs don’t have to belong to the same organization, they could send their data to different aggregators if
desired based on some contractual agreements, geolocation, etc.. The point is that a Fabric org with an MSPId can register and enroll client orgs, which then get a unique certificate – with the MSPId of the issuing org but the unique enrollment name in CN
field. Their transaction is then signed by that cert and the chaincode can extract the unique CN to apply any relevant access rules or other business logic.
Best Regards,
Mark
From: fabric@... <fabric@...>
On Behalf Of Nikos Karamolegkos Sent: Wednesday, May 5, 2021 2:13 AM To: fabric@... Subject: Re: [External] : [Hyperledger Fabric] IoT with frequent data and possibly incorrect data sometimes
So mark in order to recap, you propose each ED to be a different user which send data via REST to an aggregator (i.e a BC client) who acts as intermediate to match the data from each ED to the respective BC user? Are this EDs belong to
the same organization in order use the same aggregator?
