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

[PR #6304] [CLOSED] fix: include refreshToken in getAccessToken response #23481

New Issue
Closed
opened 2026-04-15 21:45:07 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-15 21:45:07 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/6304
Author: @GautamBytes
Created: 11/25/2025
Status: ❌ Closed

Base: canary ← Head: fix/get-access-token-fields

📝 Commits (1)

  • f560d05 fix(api): include refresh token in getAccessToken response

📊 Changes

1 file changed (+9 additions, -0 deletions)

View changed files

📝 packages/better-auth/src/api/routes/account.ts (+9 -0)

📄 Description

Description

This PR addresses Issue #6301 where the getAccessToken endpoint was missing refreshToken and refreshTokenExpiresAt in the response body, specifically when running in stateless mode (though this logic applies generally).

The Fix

I located the return statement in packages/better-auth/src/api/routes/account.ts and noticed these fields were explicitly missing from the constructed response object, despite being defined in the Zod/OpenAPI schema for this endpoint.

I have updated the response to:

  1. Include refreshToken (decrypted using decryptOAuthToken, mirroring the accessToken logic).
  2. Include refreshTokenExpiresAt.

Related Issue

Fixes #6301

Summary by cubic

Return refreshToken and refreshTokenExpiresAt in getAccessToken responses to fix missing fields (notably in stateless mode) and align with the endpoint schema. refreshToken is decrypted like accessToken, and both fields fall back to newTokens or account values as available.

Written for commit f560d05f79. Summary will update automatically on new commits.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/6304 **Author:** [@GautamBytes](https://github.com/GautamBytes) **Created:** 11/25/2025 **Status:** ❌ Closed **Base:** `canary` ← **Head:** `fix/get-access-token-fields` --- ### 📝 Commits (1) - [`f560d05`](https://github.com/better-auth/better-auth/commit/f560d05f792aae031790270305be46781554a15a) fix(api): include refresh token in getAccessToken response ### 📊 Changes **1 file changed** (+9 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `packages/better-auth/src/api/routes/account.ts` (+9 -0) </details> ### 📄 Description ## Description This PR addresses Issue #6301 where the `getAccessToken` endpoint was missing `refreshToken` and `refreshTokenExpiresAt` in the response body, specifically when running in stateless mode (though this logic applies generally). ## The Fix I located the return statement in `packages/better-auth/src/api/routes/account.ts` and noticed these fields were explicitly missing from the constructed response object, despite being defined in the Zod/OpenAPI schema for this endpoint. I have updated the response to: 1. Include `refreshToken` (decrypted using `decryptOAuthToken`, mirroring the `accessToken` logic). 2. Include `refreshTokenExpiresAt`. ## Related Issue Fixes #6301 <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Return refreshToken and refreshTokenExpiresAt in getAccessToken responses to fix missing fields (notably in stateless mode) and align with the endpoint schema. refreshToken is decrypted like accessToken, and both fields fall back to newTokens or account values as available. <sup>Written for commit f560d05f792aae031790270305be46781554a15a. Summary will update automatically on new commits.</sup> <!-- End of auto-generated description by cubic. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-15 21:45:07 -05:00
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 pull-request
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#23481
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?