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

[GH-ISSUE #3131] Oauth disabled unless linked by user #9484

New Issue
Closed
opened 2026-04-13 04:57:59 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-13 04:57:59 -05:00
Owner
Copy Link

Originally created by @Frost7994 on GitHub (Jun 22, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/3131

Is this suited for github?

  • Yes, this is suited for github

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

I want a clear and concise auth flow for my app. I have a sign in with google button. Currently it won't work if the user doesn't have a user profile from email and password which is what I expect. However, I want further restrictions so that if the user has linked a google account while signed in then they have access to signing in with google in the future. If the user hasn't linked an account however, the sign in button won't work.

Describe the solution you'd like

as mentioned above.

Describe alternatives you've considered

I've considered using hooks and checked the docs to no avail.

Additional context

No response

Originally created by @Frost7994 on GitHub (Jun 22, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/3131 ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. I want a clear and concise auth flow for my app. I have a sign in with google button. Currently it won't work if the user doesn't have a user profile from email and password which is what I expect. However, I want further restrictions so that if the user has linked a google account while signed in then they have access to signing in with google in the future. If the user hasn't linked an account however, the sign in button won't work. ### Describe the solution you'd like as mentioned above. ### Describe alternatives you've considered I've considered using hooks and checked the docs to no avail. ### Additional context _No response_
GiteaMirror added the locked label 2026-04-13 04:57:59 -05:00
GiteaMirror commented 2026-04-13 04:58:02 -05:00
Author
Owner
Copy Link

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

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

Issue Summary:

  • You requested an OAuth sign-in flow where the Google sign-in button is enabled only for users who have previously linked their Google account while signed in with email and password.
  • The goal is to restrict Google sign-in access to users with linked accounts.
  • You mentioned that the current hooks and documentation do not provide a solution for this.
  • There has been no further activity or responses on this issue.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of better-auth by commenting here.
  • If I do not hear back within 7 days, this issue will be automatically closed.

Thank you for your understanding and contribution!

<!-- gh-comment-id:3316086499 --> @dosubot[bot] commented on GitHub (Sep 21, 2025): Hi, @Frost7994. 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 requested an OAuth sign-in flow where the Google sign-in button is enabled only for users who have previously linked their Google account while signed in with email and password. - The goal is to restrict Google sign-in access to users with linked accounts. - You mentioned that the current hooks and documentation do not provide a solution for this. - There has been no further activity or responses on this issue. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of better-auth by commenting here. - If I do not hear back within 7 days, this issue will be automatically closed. Thank you 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#9484
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?