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

Updating profile information on sign-in #1138

New Issue
Closed
opened 2026-03-13 08:24:31 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-03-13 08:24:31 -05:00
Owner
Copy Link

Originally created by @Karakatiza666 on GitHub (Apr 30, 2025).

Is this suited for github?

  • Yes, this is suited for github

Is your feature request related to a problem? Please describe.

I am using a third party OAuth provider where I have RBAC configured, with generic-oauth better-auth plugin. As a part of the access/identity token I receive the JWT claim "permissions", which can be propagated with getUserInfo() and mapProfileToUser() and is stored as an additional custom field "permissions" in the User entity, which the backend can then use to authorize requests. The issue is once the User is created on the first login there is no way to automatically update user data based on UserInfo on every successive login. Triggering the update on the client does not cut it for security reasons.

Describe the solution you'd like

Either a

  1. An onLogin callback which exposes internal authentication context, which would allow calling context.internalAdapter.updateUser(), or
  2. Some way to configure the policy for refreshing User data based on UserInfo on every login.

Describe alternatives you've considered

I do not see a reasonable way to achieve this (server-side refresh of User data on login via oauth) with better-auth currently other than writing a custom plugin.
The workaround I will try out is manually updating the custom "permissions" column in the "user" built-in table with the latest profile.permissions inside the mapProfileToUser callback of the generic-oauth plugin

Additional context

No response

Originally created by @Karakatiza666 on GitHub (Apr 30, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. I am using a third party OAuth provider where I have RBAC configured, with generic-oauth better-auth plugin. As a part of the access/identity token I receive the JWT claim "permissions", which can be propagated with `getUserInfo()` and `mapProfileToUser()` and is stored as an additional custom field "permissions" in the User entity, which the backend can then use to authorize requests. The issue is once the User is created on the first login there is no way to automatically update user data based on UserInfo on every successive login. Triggering the update on the client does not cut it for security reasons. ### Describe the solution you'd like Either a 1) An onLogin callback which exposes internal authentication context, which would allow calling `context.internalAdapter.updateUser()`, or 2) Some way to configure the policy for refreshing User data based on UserInfo on every login. ### Describe alternatives you've considered I do not see a reasonable way to achieve this (server-side refresh of User data on login via oauth) with better-auth currently other than writing a custom plugin. The workaround I will try out is manually updating the custom "permissions" column in the "user" built-in table with the latest profile.permissions inside the mapProfileToUser callback of the generic-oauth plugin ### Additional context _No response_
GiteaMirror commented 2026-03-13 08:24:32 -05:00
Author
Owner
Copy Link

@Kinfe123 commented on GitHub (May 1, 2025):

Instead of approaching the onLogin callback, you could use the database hook for newly created sessions and gain access to the internal adapter as well.

@Kinfe123 commented on GitHub (May 1, 2025): Instead of approaching the onLogin callback, you could use the database hook for newly created sessions and gain access to the internal adapter as well.
GiteaMirror commented 2026-03-13 08:24:32 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (May 1, 2025):

you can set overrideUserInfoOnSignIn to true

@Bekacru commented on GitHub (May 1, 2025): you can set `overrideUserInfoOnSignIn` to `true`
GiteaMirror commented 2026-03-13 08:24:32 -05:00
Author
Owner
Copy Link

@Karakatiza666 commented on GitHub (May 1, 2025):

I did not figure out how to access the new user info in the databaseHooks.sessionCreate.after hook.
But overrideUserInfoOnSignIn option in the generic-oauth plugin that I overlooked in the docs is the perfect solution for me!

@Karakatiza666 commented on GitHub (May 1, 2025): I did not figure out how to access the new user info in the databaseHooks.sessionCreate.after hook. But `overrideUserInfoOnSignIn` option in the generic-oauth plugin that I overlooked in the docs is the perfect solution for me!
GiteaMirror commented 2026-03-13 08:24:33 -05:00
Author
Owner
Copy Link

@Karakatiza666 commented on GitHub (May 1, 2025):

@Kinfe123 could you point me to the docs/example of how to access the internal adapter instance in user code?

@Karakatiza666 commented on GitHub (May 1, 2025): @Kinfe123 could you point me to the docs/example of how to access the internal adapter instance in user code?
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#1138
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?