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

SSO: allow to sign in using providerId #720

New Issue
Closed
opened 2026-03-13 08:01:37 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-13 08:01:37 -05:00
Owner
Copy Link

Originally created by @kamilkisiela on GitHub (Feb 21, 2025).

Is this suited for github?

  • Yes, this is suited for github

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

We're trying to migrate from SuperTokens to Better Auth and the missing piece for us is the ability to sign in (SSO) using provider's id, instead of a domain, an email or an organization's slug.

We can't use email or domain, because OIDC configurations of our users do not contain domain.

Describe the solution you'd like

// same story with authClient.signIn.sso
await auth.api.signInSSO({
  body: {
    providerId: "test",
    callbackURL: "/dashboard",
  },
});

Describe alternatives you've considered

Setting up an organization, with a slug, for every organization in our app feels like unnecessary complexity, as we already have a concept of organization and member roles.

Additional context

No response

Originally created by @kamilkisiela on GitHub (Feb 21, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. We're trying to migrate from SuperTokens to Better Auth and the missing piece for us is the ability to sign in (SSO) using provider's id, instead of a domain, an email or an organization's slug. We can't use `email` or `domain`, because OIDC configurations of our users do not contain `domain`. ### Describe the solution you'd like ```ts // same story with authClient.signIn.sso await auth.api.signInSSO({ body: { providerId: "test", callbackURL: "/dashboard", }, }); ``` ### Describe alternatives you've considered Setting up an organization, with a slug, for every organization in our app feels like unnecessary complexity, as we already have a concept of organization and member roles. ### Additional context _No response_
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
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#720
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?