Skip to content

fix: support local JWKS paths in verifier CLI#11

Merged
tomjwxf merged 2 commits into
mainfrom
codex/jwks-local-paths
May 16, 2026
Merged

fix: support local JWKS paths in verifier CLI#11
tomjwxf merged 2 commits into
mainfrom
codex/jwks-local-paths

Conversation

@tomjwxf
Copy link
Copy Markdown
Contributor

@tomjwxf tomjwxf commented May 16, 2026

Summary

  • sync the standalone VeritasActa/verify repo with the current @veritasacta/verify CLI source that is already published as 0.6.0
  • update --jwks resolution to support HTTP(S), file:// URLs, absolute filesystem paths, and bare relative paths
  • report the resolved local JWKS path in the key source when a file-based JWKS is used
  • add unit coverage for absolute path, file://, relative path, and unsupported URL schemes

Why

Issues #9 and #10 report the same local-development gap: the documented sidecar JWKS test-vector flow should not require running an HTTP server. This keeps remote JWKS behavior unchanged while making offline CI and local test vectors work directly.

Verification

npm ci
npm test

Result: 223/223 passing.

Targeted checks:

node --test test/unit/jwks.test.js
node cli.js --self-test

@tomjwxf tomjwxf merged commit 79d0779 into main May 16, 2026
2 checks passed
@tomjwxf tomjwxf deleted the codex/jwks-local-paths branch May 16, 2026 10:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants