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

[GH-ISSUE #485] Missing refresh access token method implementation #8289

New Issue
Closed
opened 2026-04-13 03:21:54 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-13 03:21:54 -05:00
Owner
Copy Link

Originally created by @zAlweNy26 on GitHub (Nov 10, 2024).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/485

Is your feature request related to a problem? Please describe.
I'm not finding an easy way to refresh the access token for the social providers.

Describe the solution you'd like
I saw there is
691510711e/packages/better-auth/src/oauth2/types.ts (L40)
but it's optional and not implemented anywhere, is it normal? I think it should be required to easily refresh the access tokens of the implemented social providers. I can open a PR to implement them if you like.

Originally created by @zAlweNy26 on GitHub (Nov 10, 2024). Original GitHub issue: https://github.com/better-auth/better-auth/issues/485 **Is your feature request related to a problem? Please describe.** I'm not finding an easy way to refresh the access token for the social providers. **Describe the solution you'd like** I saw there is https://github.com/better-auth/better-auth/blob/691510711e6030a38c17b01f998cc62823bb1a06/packages/better-auth/src/oauth2/types.ts#L40 but it's optional and not implemented anywhere, is it normal? I think it should be required to easily refresh the access tokens of the implemented social providers. I can open a PR to implement them if you like.
GiteaMirror added the locked label 2026-04-13 03:21:54 -05:00
GiteaMirror commented 2026-04-13 03:21:56 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Nov 11, 2024):

Currently, none of the providers implement this internally, so if you need to refresh tokens, you'll have to handle that yourself. But, I can see this being an integration on Better Auth's side in the future. Let's leave this issue open.

<!-- gh-comment-id:2467362193 --> @Bekacru commented on GitHub (Nov 11, 2024): Currently, none of the providers implement this internally, so if you need to refresh tokens, you'll have to handle that yourself. But, I can see this being an integration on Better Auth's side in the future. Let's leave this issue open.
GiteaMirror commented 2026-04-13 03:21:56 -05:00
Author
Owner
Copy Link

@paambaati commented on GitHub (Jan 18, 2025):

@Bekacru Do you have any guidance on what this would look like?

<!-- gh-comment-id:2599588787 --> @paambaati commented on GitHub (Jan 18, 2025): @Bekacru Do you have any guidance on what this would look like?
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#8289
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?