storacha / content-claims

🦪 Implementation of the Content Claims Protocol.
Other
10 stars 1 forks source link

fix: content claims derives #74

Open alanshaw opened 18 hours ago

alanshaw commented 18 hours ago

The default derives function has very basic loose equality checks on caveat fields. Turns out this doesn't allow the service to be invoked for most of the defined capabilities when the issuer has been delegated a capability (i.e. when not using the service key to self sign the invocation). When using a delegated capability the derives function is called to figure out if you have violated any constraints.

Luckily we didn't expose this publically and we have been using the service key to sign invocations so this hasn't come up yet.

seed-deploy[bot] commented 17 hours ago
View stack outputs - **pr74-content-claims-API** Name | Value -- | -- cloudfrontUrl | https://d14505ludg8ajd.cloudfront.net functionName | pr74-content-claims-API-fn5FF616E3-5cFDuwYR725d functionUrl | https://tis7xpawq5e3evogbpcyp5erke0ruxqz.lambda-url.us-east-2.on.aws/ url | https://pr74.claims.web3.storage - **pr74-content-claims-Bucket** - **pr74-content-claims-DB**