Hyperledger Composer Permission File (permissions.acl) Explanation
#1
One of the benefits of Fabric is that you can allow and deny permissions on a participant-by-participant basis. In this thread, I will do a simple breakdown on the anatomy of a permissions.acl file.

Anatomy of a Permissions File
[Image: attachment.php?aid=57]
description: A basic description of what you would like to accomplish with this access rule.
participant: Specify what participant you would like this access rule to apply to.
operation: You have 5 different options here, CREATE, READ, UPDATE, DELETE, or ALL.
resource: Specify what resource you would this access rule to apply to. In the above example, we are selecting all resources in the network.
action: This is the action the rule is creating. Can be either ALLOW or DENY.


Attached Files Thumbnail(s)
   
Reply