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

Export better-auth password's default hash and verify functions #826

New Issue
Closed
opened 2026-03-13 08:05:57 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-03-13 08:05:57 -05:00
Owner
Copy Link

Originally created by @Manethpak on GitHub (Mar 11, 2025).

Is this suited for github?

  • Yes, this is suited for github

Is your feature request related to a problem? Please describe.

When seeding databases with mock users for development or testing, there's currently no easy way to generate proper password hashes that are compatible with better-auth's unless I switches to custom password hashing algorithm, which may result in security concerned.

Describe the solution you'd like

Export the default password hash and verify functions from the better-auth library as public API methods. This would allow developers to directly use these functions when creating mock users or seeding databases with test data.

import { password } from "better-auth";

/**
 * Hashes a plaintext password using the same algorithm as better-auth
 * @param {string} plaintext - The plaintext password to hash
 * @returns {Promise<string>} The complete hashed password string
 */
const hashedPassword = await password.hash("WeakP@ssw0rd");

/**
 * Verifies if a plaintext password matches a stored hash
 * @param {string} plaintext - The plaintext password to check
 * @param {string} hashedPassword - The previously hashed password to compare against
 * @returns {Promise<boolean>} True if the password matches, false otherwise
 */
const isValid = await password.verify("WeakP@ssw0rd", hashedPassword);

Describe alternatives you've considered

Current workarounds that I've used:

  • Creating users through the regular registration flow and extracting hashes from the database, reusing the hashes for every mock users
  • Use better-auth client, however it request the server to be available in order to seed it.
  • Implementing custom hash functions that may not match better-auth's implementation

Additional context

This feature would improve the developer experience without compromising security

Originally created by @Manethpak on GitHub (Mar 11, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. When seeding databases with mock users for development or testing, there's currently no easy way to generate proper password hashes that are compatible with better-auth's unless I switches to custom password hashing algorithm, which may result in security concerned. ### Describe the solution you'd like Export the default password hash and verify functions from the better-auth library as public API methods. This would allow developers to directly use these functions when creating mock users or seeding databases with test data. ```ts import { password } from "better-auth"; /** * Hashes a plaintext password using the same algorithm as better-auth * @param {string} plaintext - The plaintext password to hash * @returns {Promise<string>} The complete hashed password string */ const hashedPassword = await password.hash("WeakP@ssw0rd"); /** * Verifies if a plaintext password matches a stored hash * @param {string} plaintext - The plaintext password to check * @param {string} hashedPassword - The previously hashed password to compare against * @returns {Promise<boolean>} True if the password matches, false otherwise */ const isValid = await password.verify("WeakP@ssw0rd", hashedPassword); ``` ### Describe alternatives you've considered Current workarounds that I've used: - Creating users through the regular registration flow and extracting hashes from the database, reusing the hashes for every mock users - Use better-auth client, however it request the server to be available in order to seed it. - Implementing custom hash functions that may not match better-auth's implementation ### Additional context This feature would improve the developer experience without compromising security
GiteaMirror commented 2026-03-13 08:06:01 -05:00
Author
Owner
Copy Link

@namuorg commented on GitHub (Mar 11, 2025):

You can access better-auth's hash and verify functions using auth.$context (example):

const ctx = await auth.$context;
const hash = await ctx.password.hash("your-new-password");
@namuorg commented on GitHub (Mar 11, 2025): You can access `better-auth`'s hash and verify functions using `auth.$context` ([example](https://www.better-auth.com/docs/authentication/email-password#update-password)): ```typescript const ctx = await auth.$context; const hash = await ctx.password.hash("your-new-password"); ```
GiteaMirror commented 2026-03-13 08:06:03 -05:00
Author
Owner
Copy Link

@Manethpak commented on GitHub (Mar 12, 2025):

I was not aware of this the last time I checked the documentation, anyway thank you for the answer!

@Manethpak commented on GitHub (Mar 12, 2025): I was not aware of this the last time I checked the documentation, anyway thank you for the answer!
GiteaMirror commented 2026-03-13 08:06:03 -05:00
Author
Owner
Copy Link

@itisyb commented on GitHub (Apr 27, 2025):

I tried this do set a default password for my users but it returns new hash each time for example I wanted ctx.password.hash("123456");

so all my user can use that for first time login and change if they want

do you know how can I do that @namukang would be great help

@itisyb commented on GitHub (Apr 27, 2025): I tried this do set a default password for my users but it returns new hash each time for example I wanted ctx.password.hash("123456"); so all my user can use that for first time login and change if they want do you know how can I do that @namukang would be great help
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
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#826
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?