github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 07:18:56 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #7652] [MERGED] docs: add enterprise SSO migration to Supabase guide #15714

New Issue
Closed
opened 2026-04-13 10:11:17 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-13 10:11:17 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/7652
Author: @Paola3stefania
Created: 1/27/2026
Status: ✅ Merged
Merged: 1/28/2026
Merged by: @himself65

Base: canary ← Head: docs/supabase-sso-migration

📝 Commits (3)

  • 952770a add migration guide for sso enterprise
  • 2ccd1fd docs: wrap SSO migration checklist with code fences
  • e22194b Merge branch 'canary' into docs/supabase-sso-migration

📊 Changes

1 file changed (+512 additions, -34 deletions)

View changed files

📝 docs/content/docs/guides/supabase-migration-guide.mdx (+512 -34)

📄 Description

Summary by cubic

Adds an Enterprise SSO (SAML) migration path to the Supabase migration guide so teams can move SSO providers and users to Better Auth with clear steps and examples. Also refines the existing guide for safety, clarity, and large-data reliability.

  • New Features

    • SSO plugin setup and database migration.
    • Export Supabase SSO providers and migrate them to Better Auth.
    • Link SSO identities during user migration.
    • Update IdP endpoints and client code (signIn.sso).
    • Checklist and troubleshooting for SSO.

  • Refactors

    • Added backup warning and clarified email verification config.
    • Made admin/anonymous/phone plugins optional; migration warns instead of blocks.
    • Clarified env vars and noted same-database migrations.
    • Documented keyset pagination; updated run command to npx tsx.
    • Added bcrypt password config example, fixed ON CONFLICT ("id"), and improved validation messages.

Written for commit e22194b3cc. Summary will update on new commits.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/7652 **Author:** [@Paola3stefania](https://github.com/Paola3stefania) **Created:** 1/27/2026 **Status:** ✅ Merged **Merged:** 1/28/2026 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `docs/supabase-sso-migration` --- ### 📝 Commits (3) - [`952770a`](https://github.com/better-auth/better-auth/commit/952770a839eb11ada8d4bf74cbe799e182eaad94) add migration guide for sso enterprise - [`2ccd1fd`](https://github.com/better-auth/better-auth/commit/2ccd1fdff8a4feb2f37b6403a48d4497c83b9f0b) docs: wrap SSO migration checklist with code fences - [`e22194b`](https://github.com/better-auth/better-auth/commit/e22194b3cc32f4cbb6f1cb38fbd27367cbe1eb01) Merge branch 'canary' into docs/supabase-sso-migration ### 📊 Changes **1 file changed** (+512 additions, -34 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/guides/supabase-migration-guide.mdx` (+512 -34) </details> ### 📄 Description <!-- This is an auto-generated description by cubic. --> ## Summary by cubic Adds an Enterprise SSO (SAML) migration path to the Supabase migration guide so teams can move SSO providers and users to Better Auth with clear steps and examples. Also refines the existing guide for safety, clarity, and large-data reliability. - **New Features** - SSO plugin setup and database migration. - Export Supabase SSO providers and migrate them to Better Auth. - Link SSO identities during user migration. - Update IdP endpoints and client code (signIn.sso). - Checklist and troubleshooting for SSO. - **Refactors** - Added backup warning and clarified email verification config. - Made admin/anonymous/phone plugins optional; migration warns instead of blocks. - Clarified env vars and noted same-database migrations. - Documented keyset pagination; updated run command to `npx tsx`. - Added bcrypt password config example, fixed `ON CONFLICT ("id")`, and improved validation messages. <sup>Written for commit e22194b3cc32f4cbb6f1cb38fbd27367cbe1eb01. Summary will update on new commits.</sup> <!-- End of auto-generated description by cubic. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-13 10:11:17 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#15714
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?