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

[GH-ISSUE #278] Support for Custom User Session Data #16829

New Issue
Closed
opened 2026-04-15 14:49:30 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-15 14:49:30 -05:00
Owner
Copy Link

Originally created by @mamlzy on GitHub (Oct 21, 2024).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/278

I would like to request support for adding custom user session data in better-auth, similar to the functionality offered by next-auth. This feature would allow developers to include additional user-specific information within the session object that is returned after a successful authentication.

The ability to customize session data is crucial for many use cases, such as storing roles, permissions, and other metadata directly within the session. This can simplify access to user-specific information throughout an application without the need for additional database queries or custom implementations.

It would be great if better-auth could provide a way to extend the session object either through a callback function or a similar mechanism, allowing for more flexibility in handling session data.

Thank you for your consideration, and I'm looking forward to any feedback or updates on this request!

Additional context
Example of extending the session from auth.js
image

Originally created by @mamlzy on GitHub (Oct 21, 2024). Original GitHub issue: https://github.com/better-auth/better-auth/issues/278 I would like to request support for adding custom user session data in `better-auth`, similar to the functionality offered by `next-auth`. This feature would allow developers to include additional user-specific information within the session object that is returned after a successful authentication. The ability to customize session data is crucial for many use cases, such as storing roles, permissions, and other metadata directly within the session. This can simplify access to user-specific information throughout an application without the need for additional database queries or custom implementations. It would be great if `better-auth` could provide a way to extend the session object either through a callback function or a similar mechanism, allowing for more flexibility in handling session data. Thank you for your consideration, and I'm looking forward to any feedback or updates on this request! **Additional context** Example of extending the session from `auth.js` ![image](https://github.com/user-attachments/assets/51d5f7a7-7154-41f2-856f-22fbcfa716ac)
GiteaMirror added the enhancementlocked labels 2026-04-15 14:49:30 -05:00
GiteaMirror commented 2026-04-15 14:49:32 -05:00
Author
Owner
Copy Link

@nathanielrich commented on GitHub (Oct 29, 2024):

pls add this feature, this is very important, cause so we can customize everything by our own...

<!-- gh-comment-id:2443911650 --> @nathanielrich commented on GitHub (Oct 29, 2024): pls add this feature, this is very important, cause so we can customize everything by our own...
GiteaMirror commented 2026-04-15 14:49:33 -05:00
Author
Owner
Copy Link

@mikeyXmomo commented on GitHub (Oct 31, 2024):

Maybe you can try this https://www.better-auth.com/docs/concepts/typescript#additional-fields

<!-- gh-comment-id:2448830456 --> @mikeyXmomo commented on GitHub (Oct 31, 2024): Maybe you can try this https://www.better-auth.com/docs/concepts/typescript#additional-fields
GiteaMirror commented 2026-04-15 14:49:33 -05:00
Author
Owner
Copy Link

@nathanielrich commented on GitHub (Nov 1, 2024):

Maybe you can try this https://www.better-auth.com/docs/concepts/typescript#additional-fields

The issue is that this approach would add fields to the database. Instead, we need a callback function to fetch or query additional data for the session user object as needed.

<!-- gh-comment-id:2451923139 --> @nathanielrich commented on GitHub (Nov 1, 2024): > Maybe you can try this https://www.better-auth.com/docs/concepts/typescript#additional-fields The issue is that this approach would add fields to the database. Instead, we need a callback function to fetch or query additional data for the session user object as needed.
GiteaMirror commented 2026-04-15 14:49:34 -05:00
Author
Owner
Copy Link

@nathanielrich commented on GitHub (Nov 5, 2024):

pls put this on the roadmap, this is an essential feature to customize the session-user for our individual needs.

<!-- gh-comment-id:2456369845 --> @nathanielrich commented on GitHub (Nov 5, 2024): pls put this on the roadmap, this is an essential feature to customize the session-user for our individual needs.
GiteaMirror commented 2026-04-15 14:49:35 -05:00
Author
Owner
Copy Link

@romainchkr commented on GitHub (Nov 9, 2024):

I'm looking for something similar too. It would be great in order to enable Row Level Security in a Supabase backend. Do you know if there's any way to do it without that feature ??

<!-- gh-comment-id:2466406312 --> @romainchkr commented on GitHub (Nov 9, 2024): I'm looking for something similar too. It would be great in order to enable Row Level Security in a Supabase backend. Do you know if there's any way to do it without that feature ??
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 enhancement 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#16829
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?