Scenario:
You have set up external sharing (OBAC) with another Tenancy and configured an Access Policy to share a private Document Profile Asset with the external Tenancy.
The administrator of the home Tenancy can use Instaproof to verify the document.
The Asset is visible in the Asset list of the external Tenancy but when the administrator of this Tenancy tries to verify it using Instaproof it is not found.
Why this is happening:
There are three factors at play here.
First, Instaproof only searches Events.
Second, only Events that were created after the Access Policy share became active are visible to the external Tenancy.
Third, an Asset must be created before an Access Policy can become active for that Asset.
What this means:
The first Event in the life of a Document Profile Asset is the creation Event. This contains the document hash that is searched for by Instasproof BUT this Event happened before the Access Policy became active for the Asset and so it is not visible in the external Tenancy.
The result is that this Event is not visible to Instaproof.
You can check this by viewing the Event History of the Asset. In the home Tenancy the first Event is the Creation Event followed by the Change Event where the Access Policy becomes active.
In the external Tenancy the first Event will be the Change Event.
Instaproof will be able to find and verify any future versions of the shared Document Profile Asset because they are recorded after the Access Policy becomes active.
Note: this does not apply to a public Document Profile Asset because these are always visible to everybody without the need for an Access Policy.