Repository navigation
feat!: a VAC states purposes of use, and verify_chain holds a chain to them - #44
Merged
Merged
Conversation
…o them DTG Core Credentials' Purposes of Use (trustoverip/dtgwg-cred-spec#84): an optional credentialSubject.purposes on a VAC, any or a non-empty list, under context v2. verify_chain enforces the chain rule (a link stating none takes its parent's; a wider link is WidensPurposes) and reports the effective purposes. The member was refused outright before: the VAC subject denies unknown fields, so no verifier using this library could read a VAC carrying it. Breaking: new public fields on CredentialSubjectAuthority and VerifiedAuthority, and a new AuthorityError variant. Signed-off-by: Glenn Gore <glenn.g@affinidi.com>
stormer78
added a commit
to OpenVTC/verifiable-trust-infrastructure
that referenced
this pull request
Nov 10, 2026
…licate purpose (#2544) An internally tagged enum let the unit variant ignore extra members, so {"scope":"any","purposes":[...]} parsed as any, and the listed variant's set folded a duplicate purpose silently (VTI-ACL-100). Payloads of the acl tasks are held to the schema before they are parsed, but a stored entry and an SDK response are not; parse through a strict wire form instead. Found writing the same type for dtg-credentials (OpenVTC/dtg-credentials#44). Signed-off-by: Glenn Gore <glenn.g@affinidi.com>
stormer78
added a commit
that referenced
this pull request
Nov 10, 2026
A VAC's optional credentialSubject.purposes under context v2, and the chain rule in verify_chain (#44). Breaking: new public fields on CredentialSubjectAuthority and VerifiedAuthority, and AuthorityError gains WidensPurposes. Also carries the did:scid party matching (#38) and the proof-from-issuer check, released for the first time here. Signed-off-by: Glenn Gore <glenn.g@affinidi.com>
4 of 5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DTG Core Credentials' Purposes of Use (trustoverip/dtgwg-cred-spec#84): an
optional credentialSubject.purposes on a VAC, any or a non-empty list, under
context v2. verify_chain enforces the chain rule (a link stating none takes its
parent's; a wider link is WidensPurposes) and reports the effective purposes.
The member was refused outright before: the VAC subject denies unknown fields,
so no verifier using this library could read a VAC carrying it. Breaking: new
public fields on CredentialSubjectAuthority and VerifiedAuthority, and a new
AuthorityError variant.
See the CHANGELOG entry for the full surface. Tests:
authority_chain::purposescovers seven cases (none stated grantsany, narrowing, inheritance, widening refused,modelTrainingonly from a root naming it, refusal at issue, and contextv2required with an empty list refused), plus thePurposeScopeunit tests including the strict parse. Locally: fmt, clippy-D warnings,cargo test --all-features(232),--no-default-features, andcargo package --locked.The release that publishes this is a separate
chore(release)PR. VTI then pins it to checkrooms/records/get0.4 against chain purposes, and writes them inrooms/owner/issue-authority0.3.