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

Additional field with returned set to false gets included in the cached session data cookie on signin #1012

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

Originally created by @sakshamarora10 on GitHub (Apr 8, 2025).

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

  1. Create an additional field with returned set to false
  2. Enable cookie caching
  3. Sign in

Current vs. Expected behavior

Expected behaviour

Since returned is set to false for the additional field, it should not be included in the session response or in the session data stored in the cached cookie.

Current Behaviour

The field is stored in the cached cookie data

Image

What version of Better Auth are you using?

1.2.5

Provide environment information

- OS: MACOS 15.3.1
- Browser: Chrome

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

Backend

Auth config (if applicable)

import { betterAuth } from 'better-auth';

export const auth = betterAuth({
  user: {
    additionalFields: {
      riskLevel: {
        type: 'string',
        required: false,
        input: false,
        returned: false,
      },
    },
  },

  session: {
    cookieCache: {
      enabled: true,
      maxAge: 5 * 60,
    },
  },

  //...
});

Additional context

No response

Originally created by @sakshamarora10 on GitHub (Apr 8, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce 1. Create an additional field with returned set to false 2. Enable cookie caching 3. Sign in ### Current vs. Expected behavior ### Expected behaviour Since returned is set to false for the additional field, it should not be included in the session response or in the session data stored in the cached cookie. ### Current Behaviour The field is stored in the cached cookie data ![Image](https://github.com/user-attachments/assets/25265151-69bb-472a-b737-4bf1b5675e5f) ### What version of Better Auth are you using? 1.2.5 ### Provide environment information ```bash - OS: MACOS 15.3.1 - Browser: Chrome ``` ### Which area(s) are affected? (Select all that apply) Backend ### Auth config (if applicable) ```typescript import { betterAuth } from 'better-auth'; export const auth = betterAuth({ user: { additionalFields: { riskLevel: { type: 'string', required: false, input: false, returned: false, }, }, }, session: { cookieCache: { enabled: true, maxAge: 5 * 60, }, }, //... }); ``` ### Additional context _No response_
GiteaMirror commented 2026-03-13 08:17:43 -05:00
Author
Owner
Copy Link

@sakshamarora10 commented on GitHub (Apr 9, 2025):

Interestingly, all the subsequent data cookies that are generated through authClient.useSession or auth.api.getSession do not have the said field, confirming that there's a flaw in sign in implementation

@sakshamarora10 commented on GitHub (Apr 9, 2025): Interestingly, all the subsequent data cookies that are generated through `authClient.useSession ` or `auth.api.getSession` do not have the said field, confirming that there's a flaw in sign in implementation
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#1012
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?