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 #2199] Keycloak multi-tenant OAuth support #26422

New Issue
Closed
opened 2026-04-17 16:59:28 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-17 16:59:28 -05:00
Owner
Copy Link

Originally created by @pauldunn on GitHub (Apr 9, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/2199

Can I dynamically provide the clientSecret and realmId during the configuration of genericOauth?

In the example below, I’ve hardcoded the values to test Better-Auth with my Keycloak instance, and it’s functioning well. Now, I’d like to enable users to input these details through a form, which I can then pass into Better-Auth to initiate the Keycloak authentication flow.

import { betterAuth } from "better-auth";
import { genericOAuth } from "better-auth/plugins";

const realmId = "uuid here..";
const clientSecret = "secret here..";

export const auth = betterAuth({
  plugins: [
    genericOAuth({
      config: [
        {
          providerId: "keycloak",
          clientId: process.env.KEYCLOAK_CLIENT as string,
          clientSecret: clientSecret,
          discoveryUrl: `${process.env.NEXT_PUBLIC_API_URL_KEYCLOAK}/realms/${realmId}/.well-known/openid-configuration`,
          scopes: ["roles", "profile"],
        },
      ],
    }),
  ],
});
Originally created by @pauldunn on GitHub (Apr 9, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/2199 Can I dynamically provide the clientSecret and realmId during the configuration of genericOauth? In the example below, I’ve hardcoded the values to test Better-Auth with my Keycloak instance, and it’s functioning well. Now, I’d like to enable users to input these details through a form, which I can then pass into Better-Auth to initiate the Keycloak authentication flow. ``` import { betterAuth } from "better-auth"; import { genericOAuth } from "better-auth/plugins"; const realmId = "uuid here.."; const clientSecret = "secret here.."; export const auth = betterAuth({ plugins: [ genericOAuth({ config: [ { providerId: "keycloak", clientId: process.env.KEYCLOAK_CLIENT as string, clientSecret: clientSecret, discoveryUrl: `${process.env.NEXT_PUBLIC_API_URL_KEYCLOAK}/realms/${realmId}/.well-known/openid-configuration`, scopes: ["roles", "profile"], }, ], }), ], }); ```
GiteaMirror added the locked label 2026-04-17 16:59:28 -05:00
GiteaMirror commented 2026-04-17 16:59:29 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Apr 10, 2025):

You should look into the SSO plugin.
https://www.better-auth.com/docs/plugins/sso

<!-- gh-comment-id:2793577323 --> @Bekacru commented on GitHub (Apr 10, 2025): You should look into the SSO plugin. https://www.better-auth.com/docs/plugins/sso
GiteaMirror commented 2026-04-17 16:59:30 -05:00
Author
Owner
Copy Link

@gobengo commented on GitHub (May 10, 2025):

@Bekacru The SSO plugin doesn't actually provide the same features, though. It doesn't have the equivalent of the genericOauth plugin's affordances for linking oauth accounts. I too would like to be able to use the oauth2 linking functionality, but on provider id that is not statically configured in the src code, but instead added at runtime.

Is there an architectural reason why all the configured genericOauth providers must be passed as a static array?

Instead, if it worked with a plugin option getConfigForProvider(providerId: string): Promise<OauthConfig>, and that was called with whatever providerId is passed to authClient.oauth2.link or authClient.signIn.oauth2, that would allow for the client id to be pulled async from a db, or even dynamically registered with the provider just-in-time. Any reason that wouldn't work?

Upon quick glance, maybe it would just need this line to support async resolving the providerId to a config instead of only looking in the static plugin options. 8fcc758fe9/packages/better-auth/src/plugins/generic-oauth/index.ts (L402)

<!-- gh-comment-id:2868999811 --> @gobengo commented on GitHub (May 10, 2025): @Bekacru The SSO plugin doesn't actually provide the same features, though. It doesn't have the equivalent of the genericOauth plugin's affordances for [linking oauth accounts](https://www.better-auth.com/docs/plugins/generic-oauth#linking-oauth-accounts). I too would like to be able to use the oauth2 linking functionality, but on provider id that is not statically configured in the src code, but instead added at runtime. Is there an architectural reason why all the configured genericOauth providers must be passed as a static array? Instead, if it worked with a plugin option `getConfigForProvider(providerId: string): Promise<OauthConfig>`, and that was called with whatever providerId is passed to `authClient.oauth2.link` or `authClient.signIn.oauth2`, that would allow for the client id to be pulled async from a db, or even dynamically registered with the provider just-in-time. Any reason that wouldn't work? Upon quick glance, maybe it would just need this line to support async resolving the providerId to a config instead of only looking in the static plugin options. https://github.com/better-auth/better-auth/blob/8fcc758fe98640be2fc24f89e7c6259be8a52cec/packages/better-auth/src/plugins/generic-oauth/index.ts#L402
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#26422
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?