Background
As part of release planning for the for the Giza network, it was identified that there were a few different ideas about both the current way that uploader authentication to Collossus node worked currently, and how it ought to work in the future. A dedicated review and decision is required on this question for a future upgrade or release.
Terminology
Upload initiator: on-chain actor initiating ultimate extrinsic for updating data directory.Uploader: actor initiating data upload to Collossus.
Requirements
Collossus should be able to authenticate who is initiating the upload for a data object, from both static (council, working groups) or dynamic bags (members, channels) using credentials assigned by authority who initiated upload action on-chain.- The on-chain upload initiator should be able to both
- assign more than one set of credentials per object
- update credentials for objects before they have been confirmed by liaison.
Collossus must be able to provide efficiently verifiable claim of authentication step.
┆Issue is synchronized with this Asana task by Unito
Background
As part of release planning for the for the
Gizanetwork, it was identified that there were a few different ideas about both the current way that uploader authentication toCollossusnode worked currently, and how it ought to work in the future. A dedicated review and decision is required on this question for a future upgrade or release.Terminology
Upload initiator: on-chain actor initiating ultimate extrinsic for updating data directory.Uploader:actor initiating data upload toCollossus.Requirements
Collossusshould be able to authenticate who is initiating the upload for a data object, from both static (council, working groups) or dynamic bags (members, channels) using credentials assigned by authority who initiated upload action on-chain.Collossusmust be able to provide efficiently verifiable claim of authentication step.┆Issue is synchronized with this Asana task by Unito