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

A new JWT is minted for every request to getSession #1316

New Issue
Closed
opened 2026-03-13 08:32:30 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-03-13 08:32:30 -05:00
Owner
Copy Link

Originally created by @widavies on GitHub (Jun 5, 2025).

The JWT plugin will mint a new JWT every-time getSession is called: 91d504d81b/packages/better-auth/src/plugins/jwt/index.ts (L389)

Is there a way to control when the JWT is minted? I don't need a new JWT every-time it is invoked. Maybe a query parameter?

Originally created by @widavies on GitHub (Jun 5, 2025). The JWT plugin will mint a new JWT every-time `getSession` is called: https://github.com/better-auth/better-auth/blob/91d504d81bcea52a6785eec02dca1626f2b734e6/packages/better-auth/src/plugins/jwt/index.ts#L389 Is there a way to control when the JWT is minted? I don't need a new JWT every-time it is invoked. Maybe a query parameter?
GiteaMirror commented 2026-03-13 08:32:31 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Sep 4, 2025):

Hi, @widavies. I'm Dosu, and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported that the JWT plugin generates a new token on every call to getSession.
  • You inquired about options to control or limit token minting, such as using a query parameter.
  • The goal is to avoid unnecessary creation of new JWTs.
  • There have been no comments or responses on this issue so far.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of better-auth by commenting here.
  • If I don’t hear back within 7 days, this issue will be automatically closed.

Thanks for your understanding and contribution!

@dosubot[bot] commented on GitHub (Sep 4, 2025): Hi, @widavies. 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 reported that the JWT plugin generates a new token on every call to `getSession`. - You inquired about options to control or limit token minting, such as using a query parameter. - The goal is to avoid unnecessary creation of new JWTs. - There have been no comments or responses on this issue so far. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of better-auth by commenting here. - If I don’t hear back within 7 days, this issue will be automatically closed. Thanks for your understanding and contribution!
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
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#1316
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?