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

[GH-ISSUE #158] Self-Service Internal IdP with Database-Managed SSO #16784

New Issue
Closed
opened 2026-04-15 14:45:12 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-15 14:45:12 -05:00
Owner
Copy Link

Originally created by @KaanMol on GitHub (Oct 13, 2024).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/158

Currently, social identity providers (such as Google, Facebook, etc.) are hardcoded into the system. I would like to propose a feature where companies, after creating an account on the platform, can add their own internal Identity Provider (IdP) directly. This would allow users from those companies to authenticate via their internal SSO without requiring any additional deployments from me.

The key difference is that instead of having social configurations hardcoded, they should be stored in the database. A similar approach can be seen in systems like Okta, where companies can integrate their own IdP and users can sign in via SSO. More details on how Okta handles this can be found here: Okta SAML Identity Provider Setup.

As examples, when the feature is implemented, companies could either:

Have a button that says "Sign in with SSO," which prompts the user to enter their company name, looked up in the database to find the appropriate IdP.
Skip the button entirely, and upon entering an email address, the system could automatically match it to the correct company and redirect the user directly to their Identity Provider.
These are flexible options to ensure seamless authentication while allowing companies to configure their IdP without requiring any platform-side deployments.

Please let me know if this is in scope with the idea you have for V1, I have seen multiple issues where people try to use Better-Auth for a SaaS (I also am thinking about switching to it for my SaaS) and a feature like this would be amazing.

Originally created by @KaanMol on GitHub (Oct 13, 2024). Original GitHub issue: https://github.com/better-auth/better-auth/issues/158 Currently, social identity providers (such as Google, Facebook, etc.) are hardcoded into the system. I would like to propose a feature where companies, after creating an account on the platform, can add their own internal Identity Provider (IdP) directly. This would allow users from those companies to authenticate via their internal SSO without requiring any additional deployments from me. The key difference is that instead of having social configurations hardcoded, they should be stored in the database. A similar approach can be seen in systems like Okta, where companies can integrate their own IdP and users can sign in via SSO. More details on how Okta handles this can be found here: [Okta SAML Identity Provider Setup](https://help.okta.com/en-us/content/topics/security/idp-add-saml.htm). As examples, when the feature is implemented, companies could either: Have a button that says "Sign in with SSO," which prompts the user to enter their company name, looked up in the database to find the appropriate IdP. Skip the button entirely, and upon entering an email address, the system could automatically match it to the correct company and redirect the user directly to their Identity Provider. These are flexible options to ensure seamless authentication while allowing companies to configure their IdP without requiring any platform-side deployments. Please let me know if this is in scope with the idea you have for V1, I have seen multiple issues where people try to use Better-Auth for a SaaS (I also am thinking about switching to it for my SaaS) and a feature like this would be amazing.
GiteaMirror added the enhancementlocked labels 2026-04-15 14:45:12 -05:00
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 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#16784
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?