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

Generic OAuth: User data in session storage not updated when overrideUserInfo is enabled. #1160

New Issue
Closed
opened 2026-03-13 08:25:37 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-13 08:25:37 -05:00
Owner
Copy Link

Originally created by @syeng-sr on GitHub (May 5, 2025).

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

  1. Enable overrideUserInfo in the configuration for genericOAuth plugin
  2. Authenticate via an external OAuth provider
  3. Modify a user attribute in the OAuth provider
  4. Log out of the application
  5. Log in again using the same provider
  6. View session storage

Current vs. Expected behavior

Current:
When overrideUserInfo is enabled in the configuration for the genericOAuth plugin, user table is correctly updated after re-authentication. However, the session storage still contains outdated user data from the previous login.

Expected:
After logging in again, the session storage should reflect the updated user data retrieved from the OAuth provider.

What version of Better Auth are you using?

1.2.7

Provide environment information

- OS: macos
- Browser: chrome

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

Backend

Auth config (if applicable)

Additional context

No response

Originally created by @syeng-sr on GitHub (May 5, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce 1. Enable overrideUserInfo in the configuration for genericOAuth plugin 2. Authenticate via an external OAuth provider 3. Modify a user attribute in the OAuth provider 4. Log out of the application 5. Log in again using the same provider 6. View session storage ### Current vs. Expected behavior Current: When overrideUserInfo is enabled in the configuration for the genericOAuth plugin, user table is correctly updated after re-authentication. However, the session storage still contains outdated user data from the previous login. Expected: After logging in again, the session storage should reflect the updated user data retrieved from the OAuth provider. ### What version of Better Auth are you using? 1.2.7 ### Provide environment information ```bash - OS: macos - Browser: chrome ``` ### Which area(s) are affected? (Select all that apply) Backend ### Auth config (if applicable) ```typescript ``` ### Additional context _No response_
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#1160
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?