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 #7134] [MERGED] docs: update Clerk migration guide to include bcrypt configuration #32695

New Issue
Closed
opened 2026-04-17 23:26:57 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-17 23:26:57 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/7134
Author: @dngpng
Created: 1/5/2026
Status: ✅ Merged
Merged: 1/6/2026
Merged by: @himself65

Base: canary ← Head: fix/clerk-migration-guide

📝 Commits (1)

  • 7f4ba32 docs: update Clerk migration guide to include bcrypt configuration for password hashing

📊 Changes

1 file changed (+33 additions, -10 deletions)

View changed files

📝 docs/content/docs/guides/clerk-migration-guide.mdx (+33 -10)

📄 Description

Problem:

The guide didn't mention that Clerk uses bcrypt for password hashing, while Better Auth uses scrypt by default. Without configuring bcrypt, migrated users can't sign in with their existing passwords.

Solution:

  • Added a callout explaining the bcrypt requirement for Clerk migrations
  • Added installation instructions for bcrypt and @types/bcrypt
  • Added bcrypt configuration examples in the emailAndPassword.password section with hash and verify functions
  • Updated all relevant code examples to include the bcrypt configuration

Summary by cubic

Updates the Clerk migration guide to document bcrypt configuration in Better Auth so migrated users can sign in with existing passwords. Fixes sign-in failures caused by the default scrypt hash.

  • Migration
    • Added a callout explaining bcrypt vs scrypt for Clerk migrations.
    • Added install steps for bcrypt and @types/bcrypt.
    • Added a bcrypt hash/verify example in emailAndPassword.password and updated related code samples.

Written for commit 7f4ba32866. 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/7134 **Author:** [@dngpng](https://github.com/dngpng) **Created:** 1/5/2026 **Status:** ✅ Merged **Merged:** 1/6/2026 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `fix/clerk-migration-guide` --- ### 📝 Commits (1) - [`7f4ba32`](https://github.com/better-auth/better-auth/commit/7f4ba32866e6708061dfa7d5437d0b4aef7520b8) docs: update Clerk migration guide to include bcrypt configuration for password hashing ### 📊 Changes **1 file changed** (+33 additions, -10 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/guides/clerk-migration-guide.mdx` (+33 -10) </details> ### 📄 Description **Problem:** The guide didn't mention that Clerk uses bcrypt for password hashing, while Better Auth uses `scrypt` by default. Without configuring bcrypt, migrated users can't sign in with their existing passwords. **Solution:** - Added a callout explaining the bcrypt requirement for Clerk migrations - Added installation instructions for `bcrypt` and `@types/bcrypt` - Added bcrypt configuration examples in the `emailAndPassword.password` section with `hash` and `verify` functions - Updated all relevant code examples to include the bcrypt configuration <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Updates the Clerk migration guide to document bcrypt configuration in Better Auth so migrated users can sign in with existing passwords. Fixes sign-in failures caused by the default scrypt hash. - **Migration** - Added a callout explaining bcrypt vs scrypt for Clerk migrations. - Added install steps for bcrypt and @types/bcrypt. - Added a bcrypt hash/verify example in emailAndPassword.password and updated related code samples. <sup>Written for commit 7f4ba32866e6708061dfa7d5437d0b4aef7520b8. 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-17 23:26:57 -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#32695
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?