data-interoperability-panel
data-interoperability-panel copied to clipboard
Storage without initial data registration
trafficstars
The user's Authorization Agent, as well as other applications, know about storage by way of data registrations. What in the case that a user has a new storage host/pod, but no initial registrations there? (Or similar: in the case of storage from which the last registration is removed)
- How does the user tell the AA about it?
- How does the AA keep track about it until the first registration?
Does something like a private pim:storage triple seem like a useful solution here, or is there already another way by which this is achieved?
We discussed it but haven't documented it yet. We look at two complementary approaches:
- Bit manual, once the user creates a new instance of storage, they go to AA UI and paste the link in some kind of 'bootstrap storage' interaction.
- Improved: storage provider discovers access inbox for the owner of the storage. they send a simple notification with links to the storage. AA presents the user with a prompt asking if they want to bootstrap that storage.
Discussed in panel meeting of 2022-01-25:
- Location of storage is maintained by registry link.
- Nicer workflow could be achieved by having storage provider discover and notify via access inbox.
- Authorization panel can look into privileges of AA (whether AS could/should allow AA to provision).