feat(identity): wire OAuth callbacks into runtime - #28
Conversation
|
Warning Review limit reached
Next review available in: 29 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: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughGoogle 및 GitHub OAuth 콜백 라우트를 추가했습니다. 런타임은 제공자 클라이언트, ID 서비스, 감사 sink와 callback application을 구성합니다. NestJS는 callback application을 컨트롤러에 주입합니다. ChangesOAuth 콜백 런타임
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant OAuthProvider
participant OAuthHttpController
participant OAuthCallbackApplication
participant Browser
OAuthProvider->>OAuthHttpController: callback query와 cookie 전달
OAuthHttpController->>OAuthCallbackApplication: provider, query, cookie, correlation ID 전달
OAuthCallbackApplication-->>OAuthHttpController: 상태, redirect, cookie 반환
OAuthHttpController-->>Browser: no-store 응답과 보안 cookie 반환
Possibly related issues
Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@apps/identity-service/src/identity-runtime.ts`:
- Around line 288-328: Update OAuthCallbackApplication.completeAuthorization so
the success audit record uses auditWithoutThrowing, matching the failure path
and preventing audit sink I/O errors from revoking the issued session or turning
successful authentication into failure.
- Around line 288-328: Update the error handling around
OAuthCallbackApplication.completeAuthorization so only expected authentication
failures are converted through failAuthentication() and returned as 400
responses. Preserve callbackCorrelationId and requireCorrelationId validation
compatibility, while allowing transaction, database, provider, and audit errors
to retain a distinct internal/service-error type that the callback endpoint maps
to HTTP 503.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 8e72c665-6454-4de0-82b6-c711eafabd30
📒 Files selected for processing (7)
apps/identity-service/src/identity-runtime.test.tsapps/identity-service/src/identity-runtime.tsapps/identity-service/src/main.tsapps/identity-service/src/oauth-http-controller.test.tsapps/identity-service/src/oauth-http-controller.tsdocs/superpowers/plans/2026-08-03-oauth-callback-runtime-wiring-slice.mdpackage.json
Summary
Continues issue #18 by publishing the provider callback routes and wiring the callback application to production runtime dependencies.
Validation gate
Merge only after formatting, type checking, tests, build, AppGuardrail, Semgrep, Security Scan, Commercial Readiness, CodeRabbit, and all human/security review feedback complete on the exact current head with no actionable finding.
Part of #18.
Summary by CodeRabbit