update: Supabase new OIDC integration - #764
Conversation
|
Warning Review limit reached
Next review available in: 16 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: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe Kinde–Supabase integration guide was rewritten as a Quickstart covering custom OAuth configuration, Next.js authentication flows, logout handling, redirects, and verification steps. ChangesKinde–Supabase OAuth Quickstart
Estimated code review effort: 3 (Moderate) | ~20 minutes Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
Deploying kinde-docs-preview with
|
| Latest commit: |
317b1db
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://e6ba8e15.kinde-docs-preview.pages.dev |
| Branch Preview URL: | https://tamal-update-supabase-new-oi.kinde-docs-preview.pages.dev |
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 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 `@src/content/docs/integrate/third-party-tools/kinde-supabase.mdx`:
- Around line 100-114: Update the Kinde-Supabase integration guide’s setup steps
to instruct users to add /auth/callback to Supabase Authentication > URL
Configuration, including http://localhost:3000/auth/callback and the
corresponding production URL.
- Around line 188-198: Validate the next parameter in the GET callback before
using it in NextResponse.redirect, allowing only same-origin relative paths and
rejecting values such as `@attacker.example` or absolute URLs. Preserve the
existing /protected fallback and redirect valid paths using the existing origin.
- Around line 82-84: Update the Kinde setup instructions around the application
Details page to also add the local and production app origins to the Allowed
logout redirect URLs field, alongside the existing callback URL configuration,
so logout returns correctly to the app.
- Around line 77-79: Update the Aside in the Kinde/Supabase integration
documentation to instruct users to request the Kinde provider refresh token with
the `offline` scope instead of `offline_access`, and explicitly distinguish it
from Supabase’s session refresh token.
🪄 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: Repository UI
Review profile: CHILL
Plan: Pro
Run ID: 046e3f06-c067-461d-88a2-575eb3017265
📒 Files selected for processing (1)
src/content/docs/integrate/third-party-tools/kinde-supabase.mdx
This PR replaces the old minted JWT authentication to Supabase native OIDC integration. Now Kinde works as an IdP for Supabase; SB handles the session, and users are stored in the database.
Summary by CodeRabbit