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

[GH-ISSUE #146] Linking credentials to an existing social account results in “User already exists” #16778

New Issue
Closed
opened 2026-04-15 14:44:48 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-15 14:44:48 -05:00
Owner
Copy Link

Originally created by @PawelPotempa on GitHub (Oct 11, 2024).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/146

Currently, if a user signs in using social login (I’ve tested with Google), and then attempts to create a credentials-based account with the same email, a 400 User already exists error is returned instead of linking the accounts. This works fine in the reverse scenario, where a social login is attached to an existing credentials-based account.

I’m not sure if this is the intended behavior, but I wanted to raise it in case it’s an issue. Apologies if there’s something I’m missing!

Originally created by @PawelPotempa on GitHub (Oct 11, 2024). Original GitHub issue: https://github.com/better-auth/better-auth/issues/146 Currently, if a user signs in using social login (I’ve tested with Google), and then attempts to create a credentials-based account with the same email, a `400 User already exists` error is returned instead of linking the accounts. This works fine in the reverse scenario, where a social login is attached to an existing credentials-based account. I’m not sure if this is the intended behavior, but I wanted to raise it in case it’s an issue. Apologies if there’s something I’m missing!
GiteaMirror added the lockedbug labels 2026-04-15 14:44:48 -05:00
GiteaMirror commented 2026-04-15 14:44:49 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Oct 11, 2024):

yeah, that’s intentional. To add a credential account, use the user.setPassword method instead. It'll set the password and create a credential account for the user.

<!-- gh-comment-id:2407882973 --> @Bekacru commented on GitHub (Oct 11, 2024): yeah, that’s intentional. To add a credential account, use the `user.setPassword` method instead. It'll set the password and create a credential account for the user.
GiteaMirror commented 2026-04-15 14:44:50 -05:00
Author
Owner
Copy Link

@PawelPotempa commented on GitHub (Oct 11, 2024):

Got it, thanks for the clarification! However, this raises a question regarding user experience.

If I understand the user.setPassword method correctly, it only makes sense to use it when the user is already signed in. Wouldn’t it make sense to also allow the user to create a credential account via the password reset flow, if they initially signed up using a social login? If no user with the email exists, it would continue to ignore the reset attempt, as it currently does.

Right now, if a user inputs their social account email in the password reset form, the email with the reset link is sent, the user can visit the link and attempt to reset the password, however, the reset attempt fails because no credential account exists. It might feel more intuitive if this process allowed the user to set up a password, creating a credential account in the process. I believe some platforms (e.g., Spotify) use a similar flow, though I haven't checked recently.

<!-- gh-comment-id:2408172160 --> @PawelPotempa commented on GitHub (Oct 11, 2024): Got it, thanks for the clarification! However, this raises a question regarding user experience. If I understand the `user.setPassword` method correctly, it only makes sense to use it when the user is already signed in. Wouldn’t it make sense to also allow the user to create a credential account via the password reset flow, if they initially signed up using a social login? If no user with the email exists, it would continue to ignore the reset attempt, as it currently does. Right now, if a user inputs their social account email in the password reset form, the email with the reset link is sent, the user can visit the link and attempt to reset the password, however, the reset attempt fails because no credential account exists. It might feel more intuitive if this process allowed the user to set up a password, creating a credential account in the process. I believe some platforms (e.g., Spotify) use a similar flow, though I haven't checked recently.
GiteaMirror commented 2026-04-15 14:44:50 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Oct 11, 2024):

Yes, the password reset flow should allow account creation. This is a bug and it should be fixed in the next release.

<!-- gh-comment-id:2408181671 --> @Bekacru commented on GitHub (Oct 11, 2024): Yes, the password reset flow should allow account creation. This is a bug and it should be fixed in the next release.
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 bug locked
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#16778
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?