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

[GH-ISSUE #1087] lastSignIn field for users #8588

New Issue
Closed
opened 2026-04-13 03:42:23 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-13 03:42:23 -05:00
Owner
Copy Link

Originally created by @daveycodez on GitHub (Dec 31, 2024).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/1087

Is this suited for github?

  • Yes, this is suited for github

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

No response

Describe the solution you'd like

It would be great to have an easy way to figure out when a user was last logged in, and doesn't depend on sessions since those expire and can be cleaned up

Describe alternatives you've considered

Manually update user row whenever a session is created

Additional context

No response

Originally created by @daveycodez on GitHub (Dec 31, 2024). Original GitHub issue: https://github.com/better-auth/better-auth/issues/1087 ### Is this suited for github? - [X] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. _No response_ ### Describe the solution you'd like It would be great to have an easy way to figure out when a user was last logged in, and doesn't depend on sessions since those expire and can be cleaned up ### Describe alternatives you've considered Manually update user row whenever a session is created ### Additional context _No response_
GiteaMirror added the locked label 2026-04-13 03:42:23 -05:00
GiteaMirror commented 2026-04-13 03:42:24 -05:00
Author
Owner
Copy Link

@daveycodez commented on GitHub (Dec 31, 2024):

lastSignIn or lastActive would be great. Would be especially helpful when determining when to clean out anonymous users (based on last sign in)

<!-- gh-comment-id:2566717299 --> @daveycodez commented on GitHub (Dec 31, 2024): lastSignIn or lastActive would be great. Would be especially helpful when determining when to clean out anonymous users (based on last sign in)
GiteaMirror commented 2026-04-13 03:42:24 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Jan 3, 2025):

You can easily achieve this by adding a lastLogin field to the user table and using hooks to update it. And we could potentially make this a plugin, but adding it by default may not be the best idea.

<!-- gh-comment-id:2568763852 --> @Bekacru commented on GitHub (Jan 3, 2025): You can easily achieve this by adding a `lastLogin` field to the user table and using hooks to update it. And we could potentially make this a plugin, but adding it by default may not be the best idea.
GiteaMirror commented 2026-04-13 03:42:24 -05:00
Author
Owner
Copy Link

@daveycodez commented on GitHub (Jan 3, 2025):

What is the best hook to add this to?

I see there are multiple ways

https://www.better-auth.com/docs/concepts/hooks

https://www.better-auth.com/docs/concepts/database#database-hooks

I feel like this hook would be on get-session? And trigger an update to the user? So not a database hook?

<!-- gh-comment-id:2568941942 --> @daveycodez commented on GitHub (Jan 3, 2025): What is the best hook to add this to? I see there are multiple ways https://www.better-auth.com/docs/concepts/hooks https://www.better-auth.com/docs/concepts/database#database-hooks I feel like this hook would be on get-session? And trigger an update to the user? So not a database hook?
GiteaMirror commented 2026-04-13 03:42:24 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Jan 3, 2025):

assuming this is when the user last logged in, you can use db hooks after a session is created or you can also use hooks and check if there is a new session from ctx.context.newSession after specefic endpoints.

<!-- gh-comment-id:2569014150 --> @Bekacru commented on GitHub (Jan 3, 2025): assuming this is when the user last logged in, you can use db hooks after a session is created or you can also use hooks and check if there is a new session from `ctx.context.newSession` after specefic endpoints.
GiteaMirror commented 2026-04-13 03:42:24 -05:00
Author
Owner
Copy Link

@Bekacru commented on GitHub (Jan 3, 2025):

If this is to when they user is last active, that should be more of a client initated action. Use a web analytics or put a tracker that sends a request just before the user session is closed.

<!-- gh-comment-id:2569015279 --> @Bekacru commented on GitHub (Jan 3, 2025): If this is to when they user is last active, that should be more of a client initated action. Use a web analytics or put a tracker that sends a request just before the user session is closed.
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 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#8588
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?