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

[GH-ISSUE #3057] One account from one provider #9451

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

Originally created by @zispidd on GitHub (Jun 17, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/3057

Is it possible to restrict users to linking only one account from a single provider? So that a user cannot link, for example, two Google accounts to one user.

Originally created by @zispidd on GitHub (Jun 17, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/3057 Is it possible to restrict users to linking only one account from a single provider? So that a user cannot link, for example, two Google accounts to one user.
GiteaMirror added the locked label 2026-04-13 04:55:10 -05:00
GiteaMirror commented 2026-04-13 04:55:12 -05:00
Author
Owner
Copy Link

@tkrebs2 commented on GitHub (Jun 17, 2025):

You could use a hook and check if a provider with that Id already exists in your db and bounce an error message back. I'm assuming you're fetching the account information somehow, just disable the link button on the front end if > 0 providers with "x" id are found. I'm not sure of your use-case but seems there's a few options.

<!-- gh-comment-id:2981634930 --> @tkrebs2 commented on GitHub (Jun 17, 2025): You could use a hook and check if a provider with that Id already exists in your db and bounce an error message back. I'm assuming you're fetching the account information somehow, just disable the link button on the front end if > 0 providers with "x" id are found. I'm not sure of your use-case but seems there's a few options.
GiteaMirror commented 2026-04-13 04:55:13 -05:00
Author
Owner
Copy Link

@zispidd commented on GitHub (Jun 18, 2025):

I don't want to trust the user and perform checks only on the front end, but also on the back end, which is why I was wondering if there is a solution available out of the box

<!-- gh-comment-id:2983557113 --> @zispidd commented on GitHub (Jun 18, 2025): I don't want to trust the user and perform checks only on the front end, but also on the back end, which is why I was wondering if there is a solution available out of the box
GiteaMirror commented 2026-04-13 04:55:13 -05:00
Author
Owner
Copy Link

@tkrebs2 commented on GitHub (Jun 18, 2025):

No there's nothing out of the box. You would need to use listAccounts() or a db query to check the number of accounts with a certain provider id and disable your user action based on that. You could use a hook to check on the backend as well.

<!-- gh-comment-id:2984787209 --> @tkrebs2 commented on GitHub (Jun 18, 2025): No there's nothing out of the box. You would need to use `listAccounts()` or a db query to check the number of accounts with a certain provider id and disable your user action based on that. You could use a hook to check on the backend as well.
GiteaMirror commented 2026-04-13 04:55:14 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Sep 17, 2025):

Hi, @zispidd. I'm Dosu, and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You asked about restricting users to linking only one account per provider.
  • The maintainer clarified there is no built-in solution for this.
  • The recommended approach is to implement custom backend logic, such as hooks or database queries.
  • You emphasized the importance of backend validation over frontend checks.
  • The consensus is to handle this restriction via custom backend implementation.

Next Steps:

  • Please confirm if this issue is still relevant with the latest version of better-auth by commenting here.
  • If no further activity occurs, I will automatically close this issue in 7 days.

Thanks for your understanding and contribution!

<!-- gh-comment-id:3303664062 --> @dosubot[bot] commented on GitHub (Sep 17, 2025): Hi, @zispidd. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale. **Issue Summary:** - You asked about restricting users to linking only one account per provider. - The maintainer clarified there is no built-in solution for this. - The recommended approach is to implement custom backend logic, such as hooks or database queries. - You emphasized the importance of backend validation over frontend checks. - The consensus is to handle this restriction via custom backend implementation. **Next Steps:** - Please confirm if this issue is still relevant with the latest version of better-auth by commenting here. - If no further activity occurs, I will automatically close this issue in 7 days. Thanks for your understanding and contribution!
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 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#9451
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?