Repository navigation
feat: resolve did:webs (VTI-KEY-003) - #40
Merged
Merged
Conversation
Every VTI node must resolve did:webs (VTI-KEY-003), so that each party can choose its own DID method and still interoperate. The gateway's resolver had no did:webs, so a VTA or device whose DID is a did:webs could not be resolved. Take affinidi-did-resolver-cache-sdk 0.8.52 with `did-webs`. The graph holds one copy of the crate, so the feature reaches every resolver the gateway builds: the proof verifier's, the TSP self-check's and the DIDComm listener's TDKConfig. did:webs resolution runs under the same host policy as did:web/did:webvh/did:scid (public hosts only unless GATEWAY_DID_ALLOW_PRIVATE_HOSTS). The resolver side of affinidi-did-webs 0.13 needs no affinidi-keri, so no LMDB or other native library enters the build. tests/did_webs.rs creates a did:webs for a local fixture server (dev-dependency affinidi-did-webs with `create`, on affinidi-keri without default features), serves its keri.cesr and did.json, and resolves it through ResolverTuning; a second test checks the default policy refuses a private-host did:webs without connecting. Signed-off-by: Glenn Gore <glenn.g@affinidi.com>
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.
The VTI spec is making did:webs a method every VTI party resolves (trustoverip/dtgwg-vti-spec#123, VTI-KEY-003), so a VTA or device can use did:webvh, did:scid or did:webs as its DID and still reach the gateway.
affinidi-did-resolver-cache-sdk0.8.43[network]→ 0.8.52[network, did-webs]. There is one copy in the lockfile, so the proof verifier, the TSP self-check and the DIDComm listener all get the feature.cargo tree -i heedis empty). The dev-dependencyaffinidi-did-webswithcreateis for tests only.tests/did_webs.rs(offline): resolves a did:webs that a local server hosts, and the default public-only policy refuses a private-host did:webs without connecting.fmt, clippy
-D warnings,cargo test --all-targetsandcargo deny checkall pass locally.Note:
rust-version = "1.85"is already stale. The cache-sdk has needed 1.95 since 0.8.43. That's unchanged here.