The endorser service supports auto-endorsing specific types of transaction, however it is not designed to support more fine-grained control mechanisms.
Here we add a new /allow/ endpoint which can add to, delete from, and get a list of transactions which will be auto-endorsed. There is a list for:
publishing DIDs
publishing schema definitions
publishing credential definitions
When any of these lists are updated all pending transactions will be compared and if a match between one of these lists and the pending transactions is found the transaction will be endorsed.
In addition, a new configuration setting ENDORSER_REJECT_BY_DEFAULT has been introduced to control whether transactions that do not match any of the allow lists are rejected, or left pending by default
This pull request resolves #32
The endorser service supports auto-endorsing specific types of transaction, however it is not designed to support more fine-grained control mechanisms.
Here we add a new
/allow/endpoint which can add to, delete from, and get a list of transactions which will be auto-endorsed. There is a list for:When any of these lists are updated all pending transactions will be compared and if a match between one of these lists and the pending transactions is found the transaction will be endorsed.
In addition, a new configuration setting
ENDORSER_REJECT_BY_DEFAULThas been introduced to control whether transactions that do not match any of the allow lists are rejected, or left pending by defaultCurrently remaining work to be done: