Hello Manu,

The PDC policy should be done at chaincode/org level.

If you your collection policy includes some org, all org peers will have the transient data.

HLF 1.4 exemple for org2 and org3 collection.

[

  {

    "name": "secret",

    "requiredPeerCount": 0,

    "maxPeerCount": 3,

    "blockToLive": 1000000,

    "memberOnlyRead": true,

    "policy": {

      "identities": [

        {

          "role": {

            "name": "member",

            "mspId": "org2MSP"

          }

        },

        {

          "role": {

            "name": "member",

            "mspId": "org3MSP"

          }

        }

      ],

      "policy": {

        "1-of": [

          {

            "signed-by": 0

          },

          {

            "signed-by": 1

          }

        ]

      }

    }

  }

]

HLF 2.2 example for org2 and org3 collection:

[

    {

        "name": "secret",

        "requiredPeerCount": 0,

        "maxPeerCount": 3,

        "blockToLive": 1000000,

        "memberOnlyRead": true,

        "policy": "OR('org2MSP.member', 'org3MSP.member')"

    }

]

Regards,

Marcos Sarres | CEO | +55 61 98116 7866

Hi,

We are testing the latest version of HLF with PDC (private data connection). While defining roles / orgs that have access to the PDCs using collections_config.json, is there a way to have a subset of peers access/update a PDC within an organization? For example, say we have an organization ORG1 with three peers: P0, P1, P2, and a private data collection PDC1. Is it possible to restrict access to PDC1 to peers P0 and P1?

Thanks,
Manu