Endorser UI

[esune]

The endorser service would benefit from a user interface allowing authorized users to manage endorsement requests.

The UI would facilitate assessing the type of request (public DID, schema, credential definition, revocation registry, etc.) and accepting/rejecting it - this is extremely useful in scenarios where teh auto flags are not set, or are set to only process a limited set of requests.

[swcurran]

In doing this, I think we need to plan that an approval could have a scope longer than just the current transaction. The most important thing is that a first request for endorsing go through a human flow, but it is quite possible that after that has been done, anything else the author is wanting endorsed can happen automatically.

[esune]

@swcurran agreed. I think this issue would cover at least a basic UI that would allow an endorser service to be easily controlled by a human (so not relying only on the API).

As business requirements like the above are refined new features could be pushed out. I wasn't sure whether the business requirements would be part of this repo or be pushed to this repo from elsewhere - this is a related, possibly instance-specific, issue that may end up generating new details for the UI as well.

[esune]

This issue has thoughts/ideas that we might want to consider when tackling this work.

[loneil]

Adding link to rapid-development POC here https://github.com/loneil/endorser-ui
(note all the documentation in there is just the Tenant UI stuff, that needs updating)