docs(rfc): rfc 0029 — oidc bearer layer (issuer-agnostic, dex-validated), drafted - #419
Conversation
…ed), drafted Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 5 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Drafts RFC 0029 to define an issuer-agnostic OIDC/JWT bearer-token verification layer (Dex as the reference issuer for CI), additive to RFC 0026’s existing static-token authentication model, and updates mdBook navigation to include the new RFC.
Changes:
- Add RFC 0029 document describing OIDC JWT verification, claim→tenant mapping, and Dex-based acceptance strategy.
- Add RFC 0029 to the docs SUMMARY navigation.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| docs/SUMMARY.md | Adds RFC 0029 to the mdBook table of contents. |
| docs/rfcs/0029-oidc-bearer-layer.md | Introduces drafted RFC 0029 describing OIDC bearer auth layering over RFC 0026 gates. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ding Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Drafts RFC 0029: OIDC JWT verification as a second credential kind on every RFC 0026 gate — standard iss/aud/exp/JWKS validation, a configured claim → tenant mapping resolving onto the unchanged
(name, tenants)enforcement, additive to static tokens. Issuer-agnostic by construction; Dex (CNCF) is the blessed lightweight deployment and the real-container CI target (the RFC 0019 testcontainers pattern). Discharges RFC 0026 §7.1 (rotation) and §7.2 (IdP layering); machine senders ride the OTel Collectoroauth2clientextension → Dex client-credentials/token-exchange. OpenFGA is recorded as the adopt-if for future fine-grained authz (§4) — a different question, behind an already-clean seam, not needed while the model is a flat tenant allow-list. §5 lands at the specified gate per the lifecycle.Also updates epic #331's remainder to point here.
🤖 Generated with Claude Code