M3b: trust-auth RS verification crate#13
Merged
Merged
Conversation
Introduce a Cargo workspace with crates/trust-auth for resource-server JWT verification: JWKS fetch/cache, TOKEN-SPEC steps 2–8 (signature, issuer, aud, time, scope), AuthedWallet, and an Axum BearerAuth extractor with RFC 6750 error responses. Align trust-relay minting with ADR 0004 by dropping tier/att from AccessTokenClaims (reserved in TOKEN-SPEC, not emitted). Update session tests and AGENTS.md workspace layout.
Coverage reportThresholds: 80% line · 78% region (condition) ✅ Coverage meets the required threshold. Summary |
Run trust-relay and verify session JWTs through trust-auth in CI; issue hyphen-free alphanumeric nonces so EIP-4361 parsers (siwe npm) accept them.
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.
Summary
Adds
crates/trust-auth— the resource-server JWT verifier from the M3 roadmap. Rust backends (beacon-relay first) can verify trust-relay bearer tokens locally via cached JWKS without calling trust-relay on the hot path.Also aligns trust-relay token minting with ADR 0004: drops
tier/attfrom emittedAccessTokenClaims(reserved in TOKEN-SPEC, not emitted).Live E2E: new
tests/trust_auth_e2e.rsspins up trust-relay and verifies a full SIWE → session JWT flow throughtrust-auth(CI jobtrust-auth-e2e).SIWE nonce fix:
GET /v1/auth/noncenow issues 32-char hex (no hyphens) and the parser enforces alphanumeric nonces — required for EIP-4361 ABNF compliance and thesiwenpm library used in the polyglot test (#14).What's in
trust-authTokenVerifierAuthedWalletaddress(sub),scopes,jti,issuer,expires_atBearerAuthAuthorization: Bearer)verify_scope403 insufficient_scopeAuthError401/403+WWW-Authenticate: Bearer error="invalid_token"Revocation and quota remain in the adopting service (HTTP consume or future Redis replica per ADR 0003).
Workspace
Root
Cargo.tomlis now a workspace:members = [".", "crates/trust-auth"]. CIcargo fmt/clippy/test --workspacecovers both crates.Test plan
cargo fmt --check,cargo clippy -- -D warnings,cargo test --workspacetrust-authintegration tests: verify happy path, missing scope, wrong issuertests/trust_auth_e2e.rs: live trust-relay ↔ trust-auth JWT verificationtests/session.rsstill passes (notierin minted token)Follow-up
siwe+jose+viem)trust-authin beacon-relay ingest middleware (separate PR in beacon-relay repo)