Skip to content
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.

Sign up for GitHub

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

Add doc links to chaincode access control #4576

Merged
merged 1 commit into from
Dec 17, 2023
Merged

Add doc links to chaincode access control #4576

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions docs/source/private-data-arch.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <chaincode4ade.html#chaincode-access-control>`_
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
Expand Down Expand Up @@ -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 <chaincode4ade.html#chaincode-access-control>`_,
for example by calling the GetCreator() chaincode API or using the client identity
`chaincode library <https://godoc.org/github.com/hyperledger/fabric-chaincode-go/shim#ChaincodeStub.GetCreator>`__ .

Querying Private Data
Expand Down