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

[GH-ISSUE #2558] Google Provider refresh token #17881

New Issue
Closed
opened 2026-04-15 16:14:06 -05:00 by GiteaMirror · 8 comments
GiteaMirror commented 2026-04-15 16:14:06 -05:00
Owner
Copy Link

Originally created by @Mateleo on GitHub (May 6, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/2558

Is this suited for github?

  • Yes, this is suited for github

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

I need to have the refresh token.
Better Auth does not provide refresh token for the Google Provider

Describe the solution you'd like

Gather the refresh token (like Discord Provider does)

Describe alternatives you've considered

I may have to do it myself

Additional context

No response

Originally created by @Mateleo on GitHub (May 6, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/2558 ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. I need to have the refresh token. Better Auth does not provide refresh token for the Google Provider ### Describe the solution you'd like Gather the refresh token (like Discord Provider does) ### Describe alternatives you've considered I may have to do it myself ### Additional context _No response_
GiteaMirror added the locked label 2026-04-15 16:14:06 -05:00
GiteaMirror commented 2026-04-15 16:14:08 -05:00
Author
Owner
Copy Link

@zpg6 commented on GitHub (May 7, 2025):

Be sure to set accessType to offline to enable refresh tokens.

google: {
    clientId: process.env.GOOGLE_CLIENT_ID,
    clientSecret: process.env.GOOGLE_CLIENT_SECRET,
    accessType: "offline", // Required to enable refresh tokens
}

You can find out more about this in Google's guide for Using OAuth 2.0 for Web Server Applications.

Update

Tested myself and this does not save the refresh token as expected. The accessType is added to the authorizationUrl, but still null in the database.

<!-- gh-comment-id:2858312585 --> @zpg6 commented on GitHub (May 7, 2025): Be sure to set `accessType` to `offline` to enable refresh tokens. ``` google: { clientId: process.env.GOOGLE_CLIENT_ID, clientSecret: process.env.GOOGLE_CLIENT_SECRET, accessType: "offline", // Required to enable refresh tokens } ``` You can find out more about this in Google's guide for [Using OAuth 2.0 for Web Server Applications](https://developers.google.com/identity/protocols/oauth2/web-server#creatingclient). ## Update Tested myself and this does not save the refresh token as expected. The accessType is added to the authorizationUrl, but still `null` in the database.
GiteaMirror commented 2026-04-15 16:14:09 -05:00
Author
Owner
Copy Link

@Mateleo commented on GitHub (May 16, 2025):

@zpg6 Nice try :(

<!-- gh-comment-id:2887567416 --> @Mateleo commented on GitHub (May 16, 2025): @zpg6 Nice try :(
GiteaMirror commented 2026-04-15 16:14:09 -05:00
Author
Owner
Copy Link

@thisIsAdityaAtMagna commented on GitHub (May 21, 2025):

Same issue, cannot refresh the access token w/o Refresh Token.
One absurd workaround is to set the session expiry shorter that the google access token expiry that's the only way to make sure user always have a working access token.

<!-- gh-comment-id:2896124905 --> @thisIsAdityaAtMagna commented on GitHub (May 21, 2025): Same issue, cannot refresh the access token w/o Refresh Token. One absurd workaround is to set the session expiry shorter that the google access token expiry that's the only way to make sure user always have a working access token.
GiteaMirror commented 2026-04-15 16:14:10 -05:00
Author
Owner
Copy Link

@thisIsAditya commented on GitHub (May 21, 2025):

Updates on this:

	socialProviders: {
		google: {
			clientId: GOOGLE_CLIENT_ID,
			clientSecret: GOOGLE_CLIENT_SECRET,
			scope: [
			],
			accessType: "offline",
			prompt: "consent"
		}
	},

Using given code does get the refresh token @Mateleo but the down side being, the user have to consent with each login. Which is a terrible User Experience.

There is no way to check for expiry of refresh token to assert the prompt type, like:

let prompt;
if(accout.refresh_token === null || account.refreshTokenExpiresAt < now()) {
    prompt = "consent"
}
<!-- gh-comment-id:2897846904 --> @thisIsAditya commented on GitHub (May 21, 2025): Updates on this: ``` socialProviders: { google: { clientId: GOOGLE_CLIENT_ID, clientSecret: GOOGLE_CLIENT_SECRET, scope: [ ], accessType: "offline", prompt: "consent" } }, ``` Using given code does get the refresh token @Mateleo but the down side being, the user have to consent with each login. Which is a terrible User Experience. There is no way to check for expiry of refresh token to assert the prompt type, like: ``` let prompt; if(accout.refresh_token === null || account.refreshTokenExpiresAt < now()) { prompt = "consent" } ```
GiteaMirror commented 2026-04-15 16:14:11 -05:00
Author
Owner
Copy Link

@Mateleo commented on GitHub (May 22, 2025):

@thisIsAditya Thks, but it's not a viable solution for sure

<!-- gh-comment-id:2901190499 --> @Mateleo commented on GitHub (May 22, 2025): @thisIsAditya Thks, but it's not a viable solution for sure
GiteaMirror commented 2026-04-15 16:14:11 -05:00
Author
Owner
Copy Link

@jaimewukb commented on GitHub (May 30, 2025):

Has anyone managed to resolve this? I added accessType: "offline" but the refresh token still doesn't update in my db

<!-- gh-comment-id:2920988780 --> @jaimewukb commented on GitHub (May 30, 2025): Has anyone managed to resolve this? I added accessType: "offline" but the refresh token still doesn't update in my db
GiteaMirror commented 2026-04-15 16:14:12 -05:00
Author
Owner
Copy Link

@thisIsAditya commented on GitHub (Jun 16, 2025):

@jaimewukb use prompt: "consent" along with accesstype offline.
But it's not viable at all. Really bad UX

<!-- gh-comment-id:2977751894 --> @thisIsAditya commented on GitHub (Jun 16, 2025): @jaimewukb use prompt: "consent" along with accesstype offline. But it's not viable at all. Really bad UX
GiteaMirror commented 2026-04-15 16:14:14 -05:00
Author
Owner
Copy Link

@ping-maxwell commented on GitHub (Jul 8, 2025):

Hey guys - nothing you can really do much about this. It's by design from google.
I'm going to close this issue if there is nothing else.
Ping me if you have any questions or want me to reopen it for something.

<!-- gh-comment-id:3049498516 --> @ping-maxwell commented on GitHub (Jul 8, 2025): Hey guys - nothing you can really do much about this. It's by design from google. I'm going to close this issue if there is nothing else. Ping me if you have any questions or want me to reopen it for something.
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#17881
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?