poanetwork
/
quorum
mirror of https://github.com/poanetwork/quorum.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Documentation for permissioning and org key management features

This commit is contained in:
vsmk98 2019-01-17 10:06:46 +08:00
parent 061c9b85ce
commit 1142ba730e
3 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/README.md
View File

@ -8,3 +8,5 @@
* [Privacy](./privacy.md) - Sending private transactions [privacy video](https://vimeo.com/user5833792/review/210456729/8f70cfaaa5)
* [Running](./running.md) - Detailed instructions for running Quorum nodes (see also [Constellation](https://github.com/jpmorganchase/constellation), [Tessera](https://github.com/jpmorganchase/tessera))
* [API](./api.md) - new privacy API
* [Node Permissioing & Account Access Control](./permisions.md) - Overview of node permissioning and account access control features
* [Organization level transaction manager key management](./orgkey.md) - Overview of transaction manager key management at organizational level for private transactions

2
docs/orgkey.md Normal file
View File

@ -0,0 +1,2 @@
# Transaction Manager key management at Organization level
Currently when private transactions are done Quorum, the individual transaction manager (Tessera or Constellation) public keys have to be mentioned in the `privateFor` attribute. This feature allows multiple transaction manager keys to be grouped under a single organization name and at transaction level, the organization id can be passed in `privateFor` attribute instead of the keys.

2
docs/permissions.md Normal file
View File

@ -0,0 +1,2 @@
# Node Permissioning and Account Access Control
Smart contract based node permissioning and account access control has been introduced as part of this feature.