github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 06:16:18 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #2000] Add 42 provider #8997

New Issue
Closed
opened 2026-04-13 04:15:09 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-13 04:15:09 -05:00
Owner
Copy Link

Originally created by @awbx on GitHub (Mar 25, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/2000

Is this suited for github?

  • Yes, this is suited for github

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

The current better-auth package lacks support for 42 (École 42) authentication, which prevents applications from offering this sign-in option to users. Many educational tech platforms and developer tools need to support authentication with 42 accounts, as it's a prominent coding school with a large student and alumni network.

Describe the solution you'd like

I'd like better-auth to add support for 42 (École 42) as an authentication provider. The implementation should follow the existing provider pattern with:

  • OAuth2 integration with 42's API
  • Configuration options for clientId and clientSecret
  • Standard callback URL handling
  • Proper parsing of user profile data from 42's API responses
  • Supporting documentation and TypeScript type definitions

Describe alternatives you've considered

  1. Creating a custom authentication handler outside the better-auth system, but this would lack integration with the rest of the auth flow
  2. Using a generic OAuth provider configuration and adapting it manually for 42's endpoints, but this requires more work from end users and lacks official support
  3. Forking better-auth to add this feature, but this would create maintenance overhead and diverge from the main package updates

Additional context

42 is a global network of coding schools with a unique educational model, and many applications specifically targeting developers and students would benefit from this integration. The authentication uses standard OAuth2 flow, similar to existing providers. I've already created an SVG icon for use with the provider that matches the standard format used in the project.

Originally created by @awbx on GitHub (Mar 25, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/2000 ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. The current better-auth package lacks support for 42 (École 42) authentication, which prevents applications from offering this sign-in option to users. Many educational tech platforms and developer tools need to support authentication with 42 accounts, as it's a prominent coding school with a large student and alumni network. ### Describe the solution you'd like I'd like better-auth to add support for 42 (École 42) as an authentication provider. The implementation should follow the existing provider pattern with: - OAuth2 integration with 42's API - Configuration options for clientId and clientSecret - Standard callback URL handling - Proper parsing of user profile data from 42's API responses - Supporting documentation and TypeScript type definitions ### Describe alternatives you've considered 1. Creating a custom authentication handler outside the better-auth system, but this would lack integration with the rest of the auth flow 2. Using a generic OAuth provider configuration and adapting it manually for 42's endpoints, but this requires more work from end users and lacks official support 3. Forking better-auth to add this feature, but this would create maintenance overhead and diverge from the main package updates ### Additional context 42 is a global network of coding schools with a unique educational model, and many applications specifically targeting developers and students would benefit from this integration. The authentication uses standard OAuth2 flow, similar to existing providers. I've already created an SVG icon for use with the provider that matches the standard format used in the project.
GiteaMirror added the locked label 2026-04-13 04:15:09 -05:00
GiteaMirror commented 2026-04-13 04:15:11 -05:00
Author
Owner
Copy Link

@alexandre-hallaine commented on GitHub (May 27, 2025):

I think that's the best way currently :/

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

export const auth = betterAuth({
  plugins: [
    genericOAuth({
      config: [
        {
          providerId: "fortytwo",
          clientId: process.env.FORTYTWO_CLIENT_ID as string,
          clientSecret: process.env.FORTYTWO_CLIENT_SECRET as string,
          authorizationUrl: "https://api.intra.42.fr/oauth/authorize",
          tokenUrl: "https://api.intra.42.fr/oauth/token",
          userInfoUrl: "https://api.intra.42.fr/v2/me",
          scopes: ["public"],
        },
      ],
    }),
  ],
});
<!-- gh-comment-id:2914223407 --> @alexandre-hallaine commented on GitHub (May 27, 2025): I think that's the best way currently :/ ```ts import { betterAuth } from "better-auth"; import { genericOAuth } from "better-auth/plugins"; export const auth = betterAuth({ plugins: [ genericOAuth({ config: [ { providerId: "fortytwo", clientId: process.env.FORTYTWO_CLIENT_ID as string, clientSecret: process.env.FORTYTWO_CLIENT_SECRET as string, authorizationUrl: "https://api.intra.42.fr/oauth/authorize", tokenUrl: "https://api.intra.42.fr/oauth/token", userInfoUrl: "https://api.intra.42.fr/v2/me", scopes: ["public"], }, ], }), ], }); ```
GiteaMirror commented 2026-04-13 04:15:11 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Aug 26, 2025):

Hi, @awbx. 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 adding 42 (École 42) as an OAuth2 provider with clientId/clientSecret config, callback, and user profile parsing.
  • The maintainer provided a code example using the existing genericOAuth plugin to integrate 42's OAuth endpoints.
  • This solution follows the current provider pattern and enables sign-in via 42 accounts.
  • You and another user expressed positive feedback on this approach.
  • The issue was resolved with this integration example.

Next Steps

  • Please confirm if this solution still works with the latest version of better-auth or if you need further assistance.
  • If no further comments are made, I will automatically close this issue in 7 days.

Thanks for your understanding and contribution!

<!-- gh-comment-id:3224826754 --> @dosubot[bot] commented on GitHub (Aug 26, 2025): Hi, @awbx. 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 adding 42 (École 42) as an OAuth2 provider with clientId/clientSecret config, callback, and user profile parsing. - The maintainer provided a code example using the existing genericOAuth plugin to integrate 42's OAuth endpoints. - This solution follows the current provider pattern and enables sign-in via 42 accounts. - You and another user expressed positive feedback on this approach. - The issue was resolved with this integration example. **Next Steps** - Please confirm if this solution still works with the latest version of better-auth or if you need further assistance. - If no further comments are made, I will automatically close this issue in 7 days. Thanks for your understanding and contribution!
GiteaMirror commented 2026-04-13 04:15:12 -05:00
Author
Owner
Copy Link

@alexandre-hallaine commented on GitHub (Sep 3, 2025):

no!

<!-- gh-comment-id:3248888375 --> @alexandre-hallaine commented on GitHub (Sep 3, 2025): no!
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#8997
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?