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

Allow an admin to set a user password #1850

New Issue
Closed
opened 2026-03-13 09:08:02 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-03-13 09:08:02 -05:00
Owner
Copy Link

Originally created by @maelp on GitHub (Sep 5, 2025).

Is this suited for github?

  • Yes, this is suited for github

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

Right now, auth.api.setPassword requires the current user session to be given, in order to allow the user to change his password.

But there are cases (like seeding user in test database, or providing an ad-hoc mechanism to set initial passwords by the admin) where we would want to have a setPassword({userId, newPassword}) (only accessible in the backend)

Describe the solution you'd like

Allow setPassword to be called with a userId as parameter (and not using the user in the current session — which might not exist when running from an automated script)

Describe alternatives you've considered

Re-implement the creation of the corresponding account, but this is error-prone

Additional context

No response

Originally created by @maelp on GitHub (Sep 5, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. Right now, `auth.api.setPassword` requires the current user session to be given, in order to allow the user to change his password. But there are cases (like seeding user in test database, or providing an ad-hoc mechanism to set initial passwords by the admin) where we would want to have a `setPassword({userId, newPassword})` (only accessible in the backend) ### Describe the solution you'd like Allow setPassword to be called with a `userId` as parameter (and not using the user in the current session — which might not exist when running from an automated script) ### Describe alternatives you've considered Re-implement the creation of the corresponding account, but this is error-prone ### Additional context _No response_
GiteaMirror added the enhancement label 2026-03-13 09:08:02 -05:00
GiteaMirror commented 2026-03-13 09:08:06 -05:00
Author
Owner
Copy Link

@ping-maxwell commented on GitHub (Oct 6, 2025):

we have auth.api.setUserPassword which does this

@ping-maxwell commented on GitHub (Oct 6, 2025): we have auth.api.setUserPassword which does this
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 enhancement
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#1850
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?