fix: verify production OIDC identities cryptographically - #459
fix: verify production OIDC identities cryptographically#459seonghobae wants to merge 13 commits into
Conversation
|
Warning Review limit reached
Next review available in: 118 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (20)
✨ Finishing Touches 💡 2⚔️ Resolve merge conflicts 💡
🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 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 |
Superseded integration lane
This PR is closed without merge because its historical branch diverged from current protected
developand cannot be safely integrated as-is. The valuable OIDC implementation remains preserved at clean pre-reconciliation commitbfb517cf0ef1ecfab485c4cebc7d2c12c9822fae.A later attempted ancestry-only reconciliation commit (
a5a0f3cc1c7708f57cc7474098121c84c9e7cff8) proved unsafe: although it added currentdevelopas a parent, it retained the historical tree and therefore made the PR diff delete or weaken already-integrated attachment, Clearfolio, session-revocation, coverage, and security behavior. That commit is explicitly rejected as integration evidence and must never be merged.The next OIDC lane must start from the exact current protected
developtree and reapply only the intended OIDC changes frombfb517c:server/oidc.mjs, OIDC route/unit tests, OIDC documentation/CHANGELOG, package test/coverage registration, and the narrowly scoped OIDC integration inserver/app.mjs. It must preserve all current develop security and operability behavior and generate fresh exact-head CI/security/review evidence.No predecessor-head or historical Security Scan result transfers.