Skip to content
This repository has been archived by the owner on Apr 29, 2024. It is now read-only.

Require specific first resource #7

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Require specific first resource #7

wants to merge 1 commit into from

Conversation

clehner
Copy link
Contributor

@clehner clehner commented Mar 30, 2022

Require a specific value as the first resource URI to invoke CACAO-ZCAP, i.e. to authorize transforming the CACAO to a ZCAP.
The value used is a URI in this specification's namespace for a term "CacaoZcapResource2022" (not included in the JSON-LD context since it does not appear in the resulting ZCAP, only in the CACAO.

@clehner clehner marked this pull request as ready for review March 30, 2022 19:34
@chunningham
Copy link
Contributor

Can we instead infer this from the last entry being a urn:zcap:root:...?

@clehner
Copy link
Contributor Author

clehner commented Apr 5, 2022

Can we instead infer this from the last entry being a urn:zcap:root:...?

I don't think so... urn:zcap:root is only appearing in the zCap (parentCapability and capabilityChain); in the CACAO it's just a URI. https://demo.didkit.dev/2022/cacao-zcap/#root-zcap-mapping

@clehner
Copy link
Contributor Author

clehner commented Apr 7, 2022

Consensus so far seems to be to not merge this, and allow basically any CACAO to be a zCap via this specification.
Applications needing assurance that a CACAO-ZCAP was intended by its signer to be a CACAO-ZCAP will need to obtain this in an application-specific way, e.g. by checking the invocation target URI (first resource) and/or the statement string.
Edit: maybe the spec should note this as a security consideration.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants