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

[GH-ISSUE #4553] Reauth #27301

New Issue
Closed
opened 2026-04-17 18:14:11 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-17 18:14:11 -05:00
Owner
Copy Link

Originally created by @proof-llc on GitHub (Sep 10, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/4553

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 a way to reauth users, before performing a serious action like deleting their account. Reauth should work with passkeys as well.

Describe alternatives you've considered

i guess i can call signin again for a signed in user but i need to then check when login occurred - if it occurred recently, i can assume that the user was probably reauth'd and allow to proceed with serious actions.

Additional context

No response

Originally created by @proof-llc on GitHub (Sep 10, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/4553 ### 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 a way to reauth users, before performing a serious action like deleting their account. Reauth should work with passkeys as well. ### Describe alternatives you've considered i guess i can call signin again for a signed in user but i need to then check when login occurred - if it occurred recently, i can assume that the user was probably reauth'd and allow to proceed with serious actions. ### Additional context _No response_
GiteaMirror added the lockedenhancement labels 2026-04-17 18:14:11 -05:00
GiteaMirror commented 2026-04-17 18:14:12 -05:00
Author
Owner
Copy Link

@frectonz commented on GitHub (Sep 10, 2025):

There are a couple of ways to do this.

  1. You can revoke the user's session before they perform the action. [docs]
await authClient.revokeSession({
    token: "session-token"
})
  1. You can check how old the session is in your backend endpoint where you perform the action.
const { session } = await auth.api.getSession({
	headers: new Headers({
		Authorization: `Bearer ${newUser?.token}`,
	}),
});

function isOlderThanXMinutes(dateValue: Date, minutes: number): boolean {
  const now = new Date();
  const cutoff = new Date(now.getTime() - minutes * 60 * 1000);
  return dateValue < cutoff;
}

if (isOlderThanXMinutes(session.createdAt, 5) {
   // reject the request
}

you can get the same session object on your client to power your UI

const { data: session } = await authClient.getSession()

if (isOlderThanXMinutes(session.createdAt, 5) {
   // show a pop up with the sign in methods
}

You can use the regular signIn methods from the authClient to power the pop up.

<!-- gh-comment-id:3274035877 --> @frectonz commented on GitHub (Sep 10, 2025): There are a couple of ways to do this. 1. You can revoke the user's session before they perform the action. [[docs](https://www.better-auth.com/docs/concepts/session-management#revoke-session)] ```typescript await authClient.revokeSession({ token: "session-token" }) ``` 2. You can check how old the `session` is in your backend endpoint where you perform the action. ```typescript const { session } = await auth.api.getSession({ headers: new Headers({ Authorization: `Bearer ${newUser?.token}`, }), }); function isOlderThanXMinutes(dateValue: Date, minutes: number): boolean { const now = new Date(); const cutoff = new Date(now.getTime() - minutes * 60 * 1000); return dateValue < cutoff; } if (isOlderThanXMinutes(session.createdAt, 5) { // reject the request } ``` you can get the same session object on your client to power your UI ```typescript const { data: session } = await authClient.getSession() if (isOlderThanXMinutes(session.createdAt, 5) { // show a pop up with the sign in methods } ``` You can use the regular `signIn` methods from the `authClient` to power the pop up.
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#27301
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?