The problem I have at the moment is that when I generate a token for use with
daml-on-fabric (which by default has no authorization) then any token I generate for an unknown submitting party doesn’t produce an error until I try to write to the ledger.
This means in my o_beer application I can currently start a fabric network, deploy my app, create a token for an unknown party, and read from the ledger without error (just an empty response) until I try to write. I’d really like to test the token immediately after I create it to ensure that the token is valid and without having to try to write something to the ledger every time I create a token.
I also realize this may not be the best way and I should probably be using a certificate authority or something to have an authenticated Fabric ledger. If that’s the case are there any existing applications with a workflow that outlines these steps?