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 #1297] Passkey auth and session cookie cache error #8682

New Issue
Closed
opened 2026-04-13 03:50:37 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-13 03:50:37 -05:00
Owner
Copy Link

Originally created by @Valardir on GitHub (Jan 29, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/1297

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

  1. Activate the cookie session caching
  2. Try to login / add a passkey

Current vs. Expected behavior

Currently a session freshness error is thrown, I couldn't figure out how to fix it. This error does not occur when the cookie cache is disabled.

I don't know if it's really a bug. If it's intended it should be documented that passkey auth and session caching isn't compatible.

What version of Better Auth are you using?

1.1.14

Provide environment information

- Windows 11
- Chrome

Which area(s) are affected? (Select all that apply)

Client, Backend

Auth config (if applicable)

Additional context

No response

Originally created by @Valardir on GitHub (Jan 29, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/1297 ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce 1. Activate the cookie session caching 2. Try to login / add a passkey ### Current vs. Expected behavior Currently a session freshness error is thrown, I couldn't figure out how to fix it. This error does not occur when the cookie cache is disabled. I don't know if it's really a bug. If it's intended it should be documented that passkey auth and session caching isn't compatible. ### What version of Better Auth are you using? 1.1.14 ### Provide environment information ```bash - Windows 11 - Chrome ``` ### Which area(s) are affected? (Select all that apply) Client, Backend ### Auth config (if applicable) ```typescript ``` ### Additional context _No response_
GiteaMirror added the lockedbug labels 2026-04-13 03:50:37 -05:00
GiteaMirror commented 2026-04-13 03:50:40 -05:00
Author
Owner
Copy Link

@tsteckenborn commented on GitHub (Jan 29, 2025):

Can confirm. Also receiving when trying to register a passkey:

{
  "data": null,
  "error": {
    "message": "Session is not fresh",
    "code": "SESSION_IS_NOT_FRESH",
    "status": 403,
    "statusText": "FORBIDDEN"
  }
}
<!-- gh-comment-id:2622502296 --> @tsteckenborn commented on GitHub (Jan 29, 2025): Can confirm. Also receiving when trying to register a passkey: ``` { "data": null, "error": { "message": "Session is not fresh", "code": "SESSION_IS_NOT_FRESH", "status": 403, "statusText": "FORBIDDEN" } } ```
GiteaMirror commented 2026-04-13 03:50:40 -05:00
Author
Owner
Copy Link

@xLukasL commented on GitHub (Feb 1, 2025):

Can confirm.

<!-- gh-comment-id:2628777525 --> @xLukasL commented on GitHub (Feb 1, 2025): Can confirm.
GiteaMirror commented 2026-04-13 03:50:41 -05:00
Author
Owner
Copy Link

@codedusting commented on GitHub (Mar 3, 2025):

Can confirm. Also receiving when trying to register a passkey:

{
  "data": null,
  "error": {
    "message": "Session is not fresh",
    "code": "SESSION_IS_NOT_FRESH",
    "status": 403,
    "statusText": "FORBIDDEN"
  }
}

This is still not fixed. Is it?

<!-- gh-comment-id:2695316873 --> @codedusting commented on GitHub (Mar 3, 2025): > Can confirm. Also receiving when trying to register a passkey: > > ``` > { > "data": null, > "error": { > "message": "Session is not fresh", > "code": "SESSION_IS_NOT_FRESH", > "status": 403, > "statusText": "FORBIDDEN" > } > } > ``` This is still not fixed. Is it?
GiteaMirror commented 2026-04-13 03:50:41 -05:00
Author
Owner
Copy Link

@mattyx97 commented on GitHub (Mar 10, 2025):

Same problem here, again

<!-- gh-comment-id:2709973816 --> @mattyx97 commented on GitHub (Mar 10, 2025): Same problem here, again
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 bug 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#8682
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?