fix(auth): enforce credential issuance boundaries (phase 2) - #5786
Conversation
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Executive SummaryPhase 2 credential-issuance enforcement is consistent across approval, native exchange, and disclosure paths: session-only guards reject bearer/mixed auth, cookie flows are origin-gated, and bearer exchange applies Phase 1 audience/eligibility plus primary-DB pepper checks. Files Reviewed (16 files)
Previous Review Summary (commit cbf3dd1)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit cbf3dd1)Status: No Issues Found | Recommendation: Merge Executive SummaryPhase 2 credential-issuance enforcement is consistent across approval, native exchange, and disclosure paths: session-only guards reject bearer/mixed auth, cookie flows are origin-gated, and bearer exchange applies Phase 1 audience/eligibility plus primary-DB pepper checks. Files Reviewed (16 files)
Reviewed by grok-4.6 · Input: 113.9K · Output: 15.4K · Cached: 515.6K Review guidance: REVIEW.md from base branch |
cbf3dd1 to
8835f4d
Compare
Stack
Depends on #5785. This PR intentionally targets
feat/token-issuance-policy-contracts; its diff contains Phase 2 only. Retarget tomainafter Phase 1 merges, adjusting the stack if needed.Summary
no-store.Compatibility and scope
Validation
pnpm --filter web lintpassed.pnpm --filter web typecheckpassed; declaration bundling emitted external-dependency warnings.pnpm format;git diff --checkpassed.