fix(oidc): navigate backend callbacks with full reload#3047
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
More reviews will be available in 41 minutes and 57 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
WalkthroughIn both ChangesOIDC session_already_available navigation fix
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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 |
b5bfa0b to
c19f353
Compare
When Kratos reports an existing session, the login page used client-side routing for return_to. OIDC callback return paths are served by the backend through Next rewrites, so router.push could leave the browser on the callback URL without completing the flow. Force a document navigation for /oidc/* return paths while keeping client-side navigation for normal app routes.
That action is running an outdated canary CLI: ```txt Chromatic CLI v10.6.0--canary... A new major version is available (v17.4.1) ``` This specific “sentinel file not OK / not present” class of errors has been reported against old Chromatic CLI upload logic. So CI is failing during Chromatic’s asset upload/finalization step, not during your app build.
c19f353 to
18e7d83
Compare
resolves: flanksource/mission-control#3230
When Kratos reports an existing session, the login page used client-side routing for
return_to. OIDC callback return paths are served by the backend through Next rewrites, sorouter.pushcould leave the browser on the callback URL without completing the flow.Force a document navigation for
/oidc/*return paths while keeping client-side navigation for normal app routes.Summary by CodeRabbit