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

Implement authClient.linkOauth2 to enable linking generic OAuth providers #2924

New Issue
Closed
opened 2026-03-13 10:28:01 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-03-13 10:28:01 -05:00
Owner
Copy Link

Originally created by @baderj on GitHub (Feb 26, 2026).

Is this suited for github?

  • Yes, this is suited for github

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

Generic OAuth uses the sign-in method authClient.signIn.oauth2 as opposed to authClient.signIn.social for social sign-in of the built-in providers.

To link additional providers for an already logged in user there is authClient.linkSocial for social sign-in. A similar method authClient.linkOAuth2 is missing.

So currently it is not possible to link multiple generic OAuth2 providers:

  • Using authClient.signIn.oauth2 for an already signed in user will create a new user (even if allowDifferentEmail: true and the involved OAuth providers are listed as trustedProviders in the accountLinking settings).
  • Using authClient.linkSocial for a generic OAuth provider (such as Keycloak) will fail because the config is not used, e.g., the authorizationUrl is just a generic /oauth2/callback/ instead of the configured value. So the signin flow does not work.

Describe the solution you'd like

There should be a method authClient.linkOAuth2 to enable generic OAuth providers to be linked.

Describe alternatives you've considered

I considered writing my own logic to merge accounts in database hooks.

Additional context

No response

Originally created by @baderj on GitHub (Feb 26, 2026). ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. Generic OAuth uses the sign-in method `authClient.signIn.oauth2` as opposed to `authClient.signIn.social` for social sign-in of the built-in providers. To link additional providers for an already logged in user there is `authClient.linkSocial` for social sign-in. A similar method `authClient.linkOAuth2` is missing. So currently it is not possible to link multiple generic OAuth2 providers: - Using `authClient.signIn.oauth2` for an already signed in user will create a new user (even if `allowDifferentEmail: true` and the involved OAuth providers are listed as `trustedProviders` in the `accountLinking` settings). - Using `authClient.linkSocial` for a generic OAuth provider (such as Keycloak) will fail because the config is not used, e.g., the `authorizationUrl` is just a generic `/oauth2/callback/` instead of the configured value. So the signin flow does not work. ### Describe the solution you'd like There should be a method `authClient.linkOAuth2` to enable generic OAuth providers to be linked. ### Describe alternatives you've considered I considered writing my own logic to merge accounts in database hooks. ### Additional context _No response_
GiteaMirror added the enhancement label 2026-03-13 10:28:01 -05:00
GiteaMirror commented 2026-03-13 10:28:03 -05:00
Author
Owner
Copy Link

@baderj commented on GitHub (Feb 27, 2026):

Sorry I totally missed that authClient.oauth2.link exists as documented here.

The documentation User & Accounts -> Manually Linking only covers Linking Social Accounts and Linking Credential-Based Accounts, so maybe consider adding a third bullet point for Linking OAuth Accounts.

My apologies again. I should have reviewed the documentation more carefully.

@baderj commented on GitHub (Feb 27, 2026): Sorry I totally missed that `authClient.oauth2.link` exists as documented [here](https://www.better-auth.com/docs/plugins/generic-oauth#linking-oauth-accounts). The documentation [User & Accounts -> Manually Linking](https://www.better-auth.com/docs/concepts/users-accounts#manually-linking-accounts) only covers *Linking Social Accounts* and *Linking Credential-Based Accounts*, so maybe consider adding a third bullet point for *Linking OAuth Accounts*. My apologies again. I should have reviewed the documentation more carefully.
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#2924
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?