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

[GH-ISSUE #421] Feature Request: Sign-in with Identity Token #8265

New Issue
Closed
opened 2026-04-13 03:20:51 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-13 03:20:51 -05:00
Owner
Copy Link

Originally created by @oktaysenkan on GitHub (Nov 5, 2024).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/421

Is your feature request related to a problem? Please describe.
I need to implement authentication with an OIDC ID token, but the current library doesn’t provide a direct method for this.

Describe the solution you'd like
I would like a method similar to supabase.auth.signInWithIdToken that allows signing in with an OIDC ID token.

Additional context
This example works with native login prompt.

import * as AppleAuthentication from 'expo-apple-authentication';

const credential = await AppleAuthentication.signInAsync({
    requestedScopes: [
        AppleAuthentication.AppleAuthenticationScope.FULL_NAME,
        AppleAuthentication.AppleAuthenticationScope.EMAIL,
    ],
});

console.log(credential.identityToken)

image

Supabase Reference

Originally created by @oktaysenkan on GitHub (Nov 5, 2024). Original GitHub issue: https://github.com/better-auth/better-auth/issues/421 **Is your feature request related to a problem? Please describe.** I need to implement authentication with an OIDC ID token, but the current library doesn’t provide a direct method for this. **Describe the solution you'd like** I would like a method similar to `supabase.auth.signInWithIdToken` that allows signing in with an OIDC ID token. **Additional context** This example works with native login prompt. ```tsx import * as AppleAuthentication from 'expo-apple-authentication'; const credential = await AppleAuthentication.signInAsync({ requestedScopes: [ AppleAuthentication.AppleAuthenticationScope.FULL_NAME, AppleAuthentication.AppleAuthenticationScope.EMAIL, ], }); console.log(credential.identityToken) ``` ![image](https://github.com/user-attachments/assets/e8626b85-cd04-4e03-a80a-4c04db7d0e9a) [Supabase Reference](https://supabase.com/docs/reference/javascript/auth-signinwithidtoken)
GiteaMirror added the locked label 2026-04-13 03:20:51 -05:00
GiteaMirror commented 2026-04-13 03:20:53 -05:00
Author
Owner
Copy Link

@abegehr commented on GitHub (Nov 10, 2024):

This is great! Using the Apple identityToken, do we still have to set clientId and clientSecret on the apple provider? If so, when generating the apple clientSecret it needs to have an expiration date. Is it fine to use a super-long-lived token for clientSecret? https://developer.apple.com/documentation/accountorganizationaldatasharing/creating-a-client-secret

<!-- gh-comment-id:2466757246 --> @abegehr commented on GitHub (Nov 10, 2024): This is great! Using the Apple identityToken, do we still have to set clientId and clientSecret on the apple provider? If so, when generating the apple clientSecret it needs to have an expiration date. Is it fine to use a super-long-lived token for clientSecret? https://developer.apple.com/documentation/accountorganizationaldatasharing/creating-a-client-secret
GiteaMirror commented 2026-04-13 03:20:53 -05:00
Author
Owner
Copy Link

@abegehr commented on GitHub (Nov 10, 2024):

Max. token lifetime that apple excepts seems to be 6 months: https://github.com/Faruqt/generate-apple-client-secret-key?tab=readme-ov-file#generate-apple-client-secret-key - therefore best-case would be to generate a clientSecret in the application itself from the p8-key.

<!-- gh-comment-id:2466761201 --> @abegehr commented on GitHub (Nov 10, 2024): Max. token lifetime that apple excepts seems to be 6 months: https://github.com/Faruqt/generate-apple-client-secret-key?tab=readme-ov-file#generate-apple-client-secret-key - therefore best-case would be to generate a clientSecret in the application itself from the p8-key.
GiteaMirror commented 2026-04-13 03:20:53 -05:00
Author
Owner
Copy Link

@abegehr commented on GitHub (Nov 10, 2024):

In case, we want to generate the apple client secret on-the-go in the future, here is a sample: https://github.com/WcaleNieWolny/capgo-social-login-backend-demo/blob/main/index.ts#L25

<!-- gh-comment-id:2466844842 --> @abegehr commented on GitHub (Nov 10, 2024): In case, we want to generate the apple client secret on-the-go in the future, here is a sample: https://github.com/WcaleNieWolny/capgo-social-login-backend-demo/blob/main/index.ts#L25
GiteaMirror commented 2026-04-13 03:20:54 -05:00
Author
Owner
Copy Link

@abegehr commented on GitHub (Nov 10, 2024):

I finally got "Sign-in with Apple" working on my iOS Capacitor app (should be the same for all hybrid platforms):

The main thing that tripped me up, is that better-auth requires clientId and clientSecret on socialProviders.apple in config -> this is where you're place the service id and jwt secret generated from p8-file for "Sign-in with Apple" on web.
However on native iOS, it doesn't use the service id but the app id (bundle id) as client id, so if using the service id as clientId in signIn.social() with idToken, it throws an error: JWTClaimValidationFailed: unexpected "aud" claim value.

For iOS native "SignIn with Apple" with idToken, it expects the app/bundle id as clientId and doesn't require the clientSecret.

<!-- gh-comment-id:2466911181 --> @abegehr commented on GitHub (Nov 10, 2024): I finally got "Sign-in with Apple" working on my iOS Capacitor app (should be the same for all hybrid platforms): The main thing that tripped me up, is that better-auth requires `clientId` and `clientSecret` on `socialProviders.apple` in config -> this is where you're place the service id and jwt secret generated from p8-file for "Sign-in with Apple" on web. However on native iOS, it doesn't use the service id but the app id (bundle id) as client id, so if using the service id as clientId in `signIn.social()` with `idToken`, it throws an error: `JWTClaimValidationFailed: unexpected "aud" claim value`. For iOS native "SignIn with Apple" with idToken, it expects the app/bundle id as `clientId` and doesn't require the `clientSecret`.
GiteaMirror commented 2026-04-13 03:20:54 -05:00
Author
Owner
Copy Link

@tlebeitsuk commented on GitHub (Dec 12, 2024):

I finally got "Sign-in with Apple" working on my iOS Capacitor app (should be the same for all hybrid platforms):

The main thing that tripped me up, is that better-auth requires clientId and clientSecret on socialProviders.apple in config -> this is where you're place the service id and jwt secret generated from p8-file for "Sign-in with Apple" on web. However on native iOS, it doesn't use the service id but the app id (bundle id) as client id, so if using the service id as clientId in signIn.social() with idToken, it throws an error: JWTClaimValidationFailed: unexpected "aud" claim value.

For iOS native "SignIn with Apple" with idToken, it expects the app/bundle id as clientId and doesn't require the clientSecret.

Thanks for the heads up! This should be added to the docs.

<!-- gh-comment-id:2538078924 --> @tlebeitsuk commented on GitHub (Dec 12, 2024): > I finally got "Sign-in with Apple" working on my iOS Capacitor app (should be the same for all hybrid platforms): > > The main thing that tripped me up, is that better-auth requires `clientId` and `clientSecret` on `socialProviders.apple` in config -> this is where you're place the service id and jwt secret generated from p8-file for "Sign-in with Apple" on web. However on native iOS, it doesn't use the service id but the app id (bundle id) as client id, so if using the service id as clientId in `signIn.social()` with `idToken`, it throws an error: `JWTClaimValidationFailed: unexpected "aud" claim value`. > > For iOS native "SignIn with Apple" with idToken, it expects the app/bundle id as `clientId` and doesn't require the `clientSecret`. Thanks for the heads up! This should be added to the docs.
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#8265
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?