Likely related to #57 and #58 which @dpetran has worked on
We have two very related user story needs:
We need to ensure that a service like Nexus, which allows users not to sign their own requests, but where the identity is known to Nexus , to still be able to audit commits for who transacted them.
We should allow transactions to be issued such that any arbitrary metadata can be applied to the txn/commit itself (as opposed to data entities in the dataset) -- this is how we accomplished this in v2
For item#1, a few notes:
Whatever way we introduce to allow a transaction to be "issued on behalf of X", this should obviously be separate from how we record the cryptographically-provable issuance of a txn by a particular did/identity
With that said, we might still want to give this metadata about "issued on behalf of X" to have slightly higher significance than arbitrary metadata (e.g. we might want the /history API to accept a syntax like showAuth: true, which, when supplied to a /history request, would return the "signer" AND (if it exists) this "issuer by proxy"
I am not sure whether Fluree should need to do a lookup on this identity "X" if a transaction is "issued on behalf of X". On the one hand, this was how we did it in v2 (i.e. an entity "Y" could transact on behalf of "X" only if there was a delegated authority relationship from "X" --> "Y"). However, in Nexus, when a dataset owner adds entity "X" as a collaborator with write access to a dataset, it is important that entity "X" does not need to be an identity known to the dataset (because Nexus manages that identity and its relationship to the dataset externally to the dataset itself)
Description
We have two very related user story needs:
For item#1, a few notes:
/historyAPI to accept a syntax likeshowAuth: true, which, when supplied to a/historyrequest, would return the "signer" AND (if it exists) this "issuer by proxy"