hyperledger composer essential acls |
If you don't know how to setup hyperledger composer read this post.
I almost gave 5 days 😅 to add an asset via participants other than Admin. As I get an error about some permission for that kind of participant I was adding that resource permission to that participants ACL.
.. .. And I have almost given 8 system permissions including network and asset registry resources. Actually, I don't find a solution on any blog or documentation, but (guess what? 😳) I found a solution on someone's GitHub sample project.
That I am sharing here.
Essentials ACL's that has to be applied
[ at least in case you are going to use composer-rest-server ]
// Give NetworkAdmin User Full Access To Every Resouces //
rule NetworkAdminUser {
description: "network administrators full access to user resources"
participant: "org.hyperledger.composer.system.NetworkAdmin"
operation: ALL
resource: "**"
action: ALLOW
}
rule NetworkAdminSystem {
description: "network admin full access to system resources"
participant: "org.hyperledger.composer.system.NetworkAdmin"
operation: ALL
resource: "org.hyperledger.composer.system.**"
action: ALLOW
}
// This is a critical ACL. It provides every participant access to // Just composer system.
// on top of which your system & composer-rest-server going to work.
rule SystemACL {
description: "System ACL to permit all access"
participant: "org.hyperledger.composer.system.Participant"
operation: ALL
resource: "org.hyperledger.composer.system.**"
action: ALLOW
}
// After upper three rules, you can define your systems ACL's
rule MyRules {
description: "System ACL to permit all access"
participant: "com.mchampaneri.project.Garage"
operation: ALL
resource: "com.mchampaneri.project.Car"
action: ALLOW
}
Hope You will find this useful.
Stay tuned for further Posts on hyper ledger fabric composer.
Have a nice Day :)
Comments
Post a Comment