From 9b717afa4585bfb0d0f7cac2fd31a67ee3f438dd Mon Sep 17 00:00:00 2001 From: Dave Enyeart Date: Sun, 17 Dec 2023 06:14:25 -0500 Subject: [PATCH] Add doc links to chaincode access control (#4576) Add doc links to chaincode access control in the private data doc. Signed-off-by: David Enyeart --- docs/source/private-data-arch.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/source/private-data-arch.rst b/docs/source/private-data-arch.rst index e16fe698b47..8cd8debe271 100644 --- a/docs/source/private-data-arch.rst +++ b/docs/source/private-data-arch.rst @@ -166,7 +166,8 @@ Since implicit private data collections are not explicitly defined, it is not possible to set the additional collection properties. Specifically, ``memberOnlyRead`` and ``memberOnlyWrite`` are not available, meaning that access control for clients reading data from or writing data to -an implicit private data collection must be encoded in the chaincode on the organization's peer. +an implicit private data collection must be encoded in the `chaincode logic `_ +on the organization's peer. Furthermore, ``blockToLive`` is not available, meaning that private data is never automatically purged. The properties ``requiredPeerCount`` and ``maxPeerCount`` can however be set in the peer's core.yaml @@ -325,8 +326,8 @@ configuration definitions and how to set them, refer back to the .. note:: If you would like more granular access control, you can set ``memberOnlyRead`` and ``memberOnlyWrite`` to false (implicit collections always behave as if ``memberOnlyRead`` and ``memberOnlyWrite`` are false). You can then apply your - own access control logic in chaincode, for example by calling the GetCreator() - chaincode API or using the client identity + own `access control logic in chaincode `_, + for example by calling the GetCreator() chaincode API or using the client identity `chaincode library `__ . Querying Private Data