fix: support current auth Provider and Verifier compositions - #20
Merged
Merged
Conversation
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
1 participant
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.
Provin's released composition uses the old collector context and implicit endpoint/key wiring. Substituting the current auth Provider and Verifier failed to compile, then failed at startup and denied every scopeless DID request.
This change aligns Zod throughout workspace/generated dependency graphs, adapts the verified-subject and untrusted-context APIs while retaining 0.3.x compatibility, wires the separated JWKS/key-resolver modules, and updates generated configuration. An explicit Owner DID rule admits only the declared request surface; other policy groups and downstream registry ACLs still decide permissions. Current Verifier issuer/audience checks remain enabled.
Validation: build/typecheck/full tests with released dependencies and locally packed candidate Provider
8f97fa6/ Verifiera7465a2; generated apps build, typecheck and boot with candidate packages; real DID issuance and tampered-signature rejection; HTTP allow/deny including non-Owner subjects and wrong issuer/audience. Three new collector regressions failed before the fix and passed afterward.Generated auth release pins remain unchanged.
docs/upstream-compatibility.mddescribes the dependency/config migration and expiry-based revocation boundary; no package or image is published by this PR.Also refresh four vulnerable transitive dependencies (js-yaml, qs, nanoid and brace-expansion) within existing compatible ranges and add a CI audit gate. The updated full dependency audit reports zero advisories.