Define & implement endorsement policy support

[hyperledger]

Define & implement endorsement policy support

[mbrandenburger]

Looking at Fabric v2 documentation, I don't see how the designated peer can be implemented using the provided primitives.

https://hyperledger-fabric.readthedocs.io/en/release-2.0/endorsement-policies.html?highlight=default%20endorsement%20policie#endorsement-policy-syntax

[mbrandenburger]

I guess a OR('Org1.peer') is the closest what we can get, however, this policy does not express that we only want a single specific peer and therefore any peer or Org1 can endorse.

[mbrandenburger]

I guess we have two options here.

1. Just say endorsement policy is ignored for MVP and in Peer_CLI we set it to any org and enforce the designated peer/enclave through fpc-vscc and ERCC. We could restrict ERCC to register only a single enclave per chaincode. In fpc-vscc we invalidate every transaction from an enclave that is not registered. The documentation should mention that any endorsement policy is ignored for FPC_Chaincodes.

2. Implement CCKeyImport/Export and support any form of `OR(...) endorsement policy.

[g2flyer]

I guess a OR('Org1.peer') is the closest what we can get,

That would have been my take.

however, this policy does not express that we only want a single specific peer and therefore any peer or Org1 can endorse.

I don't think we have to implement it to the letter, we can further restrict it by saying only a single peer for that org will have createenclave called for it and the clients have to make sure that they call the correct peer ...