Update the CLIs & Console to support the new content serve authorization flow #207
Assignees
Comments
fforbeck
changed the title
This was referenced Dec 13, 2024
|
fforbeck
changed the title
fforbeck
changed the title
fforbeck
added a commit
to storacha/upload-service
that referenced
this issue
Dec 19, 2024
…ay (#99) To enable a gateway to serve content from a specific space, we must ensure that the space owner delegates the `space/content/serve/*` capability to the Gateway. This delegation allows the Gateway to serve content and log egress events appropriately. I created a new function `authorizeContentServe` for this implementation and included it in the `createSpace` flow. This is a breaking change because now the user is forced to provide the DIDs of the Content Serve services, and the connection, or skip the authorization flow. Additionally, with the `authorizeContentServe` function, we can implement a feature in the Console App that enables users to explicitly authorize the Freeway Gateway to serve content from existing/legacy spaces. - **New Functionality:** - Added a new function, `authorizeContentServe`, in the `w3up-client` module to facilitate the delegation process. Integrated it with the `createdSpace` flow. - It also sets the Storacha Gateway as the default content server service in case the user doesn't provide any in the `createSpace` call, and doesn't use the `skipGatewayAuthorization=true` flag. - **Testing:** Introduced test cases to verify the authorization of specified gateways. - **Fixes:** Resolved issues with previously broken test cases (Egress Record). ### Related Issues - storacha/project-tracking#158 - storacha/project-tracking#160 - storacha/project-tracking#207 - storacha#1604 - Resolves storacha/project-tracking#196
fforbeck
added a commit
to storacha/w3cli
that referenced
this issue
Dec 19, 2024
### Context We must ensure that the space owner delegates the `space/content/serve/*` capability to the Gateway. This delegation allows the Gateway to serve content and log egress events appropriately. ### Changes I've updated the CLI to enable the new gateway content serve authorization flow when creating a space. This is a breaking change because now the user is forced to provide the DIDs of the Content Serve services, and the service endpoint, or skip the authorization flow. ### Related Issues - storacha/project-tracking#158 - storacha/project-tracking#160 - storacha/project-tracking#207 - Resolves storacha/project-tracking#196
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
w3cliis using a very old version of thew3up-client(v14.1.1), we will need to update to the latest version (17.1.0) and solve any breaking changes.storacha/clineeds to be updated as well to support the newcreateSpacefunction.w3ui/corewas updated to use thestoracha/cli, so we first need to release thestoracha/cliand then update and release thew3ui/corelib.w3ui/corewhich needs to be updated,coreis usingstoracha/clientinstead ofw3up-client, so we need to sync theupload-servicerepo with thew3uprepo to get the latest changes that support the content serve authorization flow.The text was updated successfully, but these errors were encountered: