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

Add username plugin option to allow the client to change username every x seconds #1502

New Issue
Closed
opened 2026-03-13 08:43:42 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-03-13 08:43:42 -05:00
Owner
Copy Link

Originally created by @PandeoF1 on GitHub (Jul 15, 2025).

Is this suited for github?

  • Yes, this is suited for github

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

The goal is to disallow the user to change the username every 1 seconds...

And i want to have this parameters directly in the plugin to disallow the user to bypass my front by using the better auth api directly

Describe the solution you'd like

Add a lastUsernameUpdate to the username and a variable in the plugin to store the interval between two update
And at each update, compare them to check if it's under the interval limit

Describe alternatives you've considered

Use ratelimits, but it's dangerous because it can be cleared if the cache is cleared (for memory, redis ect ect)

Additional context

No response

Originally created by @PandeoF1 on GitHub (Jul 15, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. The goal is to disallow the user to change the username every 1 seconds... And i want to have this parameters directly in the plugin to disallow the user to bypass my front by using the better auth api directly ### Describe the solution you'd like Add a lastUsernameUpdate to the username and a variable in the plugin to store the interval between two update And at each update, compare them to check if it's under the interval limit ### Describe alternatives you've considered Use ratelimits, but it's dangerous because it can be cleared if the cache is cleared (for memory, redis ect ect) ### Additional context _No response_
GiteaMirror added the enhancementplugin labels 2026-03-13 08:43:42 -05:00
GiteaMirror commented 2026-03-13 08:43:46 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Oct 14, 2025):

Hi, @PandeoF1. I'm Dosu (https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested a plugin feature to limit how often clients can change usernames by adding a configurable interval.
  • The plugin would track the last update time to enforce this limit.
  • This approach aims to prevent users from bypassing front-end restrictions via direct API calls.
  • You prefer this over rate limiting due to concerns about cache clearing making rate limits unreliable.
  • There has been no further activity or comments on this issue.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of better-auth by commenting here.
  • If I don’t hear back within 7 days, this issue will be automatically closed.

Thanks for your understanding and contribution!

@dosubot[bot] commented on GitHub (Oct 14, 2025): Hi, @PandeoF1. I'm Dosu (https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested a plugin feature to limit how often clients can change usernames by adding a configurable interval. - The plugin would track the last update time to enforce this limit. - This approach aims to prevent users from bypassing front-end restrictions via direct API calls. - You prefer this over rate limiting due to concerns about cache clearing making rate limits unreliable. - There has been no further activity or comments on this issue. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of better-auth by commenting here. - If I don’t hear back within 7 days, this issue will be automatically closed. Thanks for your understanding and contribution!
GiteaMirror commented 2026-03-13 08:43:48 -05:00
Author
Owner
Copy Link

@PandeoF1 commented on GitHub (Oct 14, 2025):

Yes it could be a nice feature

@PandeoF1 commented on GitHub (Oct 14, 2025): Yes it could be a nice feature
GiteaMirror commented 2026-03-13 08:43:49 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Jan 13, 2026):

Hi, @PandeoF1. I'm Dosu, and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested a plugin feature to limit how often clients can change usernames by adding a configurable interval and tracking the last update time.
  • The goal is to prevent bypassing front-end restrictions via direct API calls.
  • The issue was marked as stale due to inactivity.
  • You confirmed that it could be a nice feature.
  • No further updates or developments have occurred since your confirmation.

Next Steps:

  • Please let me know if this feature request is still relevant to the latest version of better-auth by commenting on this issue.
  • If I do not hear back within 7 days, the issue will be automatically closed.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Jan 13, 2026): Hi, @PandeoF1. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested a plugin feature to limit how often clients can change usernames by adding a configurable interval and tracking the last update time. - The goal is to prevent bypassing front-end restrictions via direct API calls. - The issue was marked as stale due to inactivity. - You confirmed that it could be a nice feature. - No further updates or developments have occurred since your confirmation. **Next Steps:** - Please let me know if this feature request is still relevant to the latest version of better-auth by commenting on this issue. - If I do not hear back within 7 days, the issue will be automatically closed. Thank you for your understanding and contribution!
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 plugin
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#1502
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?