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

Add signUpOnVerification support for emailOTP plugin to auto-generate temp name #2100

New Issue
Closed
opened 2026-03-13 09:27:13 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-03-13 09:27:13 -05:00
Owner
Copy Link

Originally created by @rohityadav-sas on GitHub (Oct 10, 2025).

Is this suited for github?

  • Yes, this is suited for github

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

Currently, the emailOTP plugin does not provide a signUpOnVerification option similar to the phoneNumber plugin.
This makes it difficult to automatically create a user profile (e.g., generate a random or derived username) when signing up with email OTP.
For example, while phoneNumber has getTempEmail and getTempName, the same behavior is missing for emailOTP.

Describe the solution you'd like

It would be helpful if the emailOTP plugin included an optional signUpOnVerification configuration similar to the phoneNumber plugin allowing developers to define:

  • A getTempName function to generate a random name

Example:

emailOTP({
  overrideDefaultEmailVerification: true,
  async sendVerificationOTP({ email, otp, type }) {
    // existing code...
  },
  signUpOnVerification: {
    getTempName: (email) => `User-${email.split('@')[0]}`
  }
})

Describe alternatives you've considered

I’m considering using Before Hooks to handle user creation and generate temporary names as a workaround, but I’m not sure if this is the best approach. I’d like confirmation from others on whether this is the recommended way to handle it for now.

Additional context

In the phoneNumber plugin, we can generate temporary user data like:

signUpOnVerification: {
  getTempEmail: (phoneNumber) => `temp-${phoneNumber}@example.com`,
  getTempName: (phoneNumber) => `User-${phoneNumber.slice(-4)}`
}
Originally created by @rohityadav-sas on GitHub (Oct 10, 2025). ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. Currently, the `emailOTP` plugin does not provide a `signUpOnVerification` option similar to the `phoneNumber` plugin. This makes it difficult to automatically create a user profile (e.g., generate a random or derived username) when signing up with email OTP. For example, while phoneNumber has getTempEmail and getTempName, the same behavior is missing for emailOTP. ### Describe the solution you'd like It would be helpful if the `emailOTP` plugin included an optional `signUpOnVerification` configuration similar to the `phoneNumber` plugin allowing developers to define: - A `getTempName` function to generate a random name Example: ``` emailOTP({ overrideDefaultEmailVerification: true, async sendVerificationOTP({ email, otp, type }) { // existing code... }, signUpOnVerification: { getTempName: (email) => `User-${email.split('@')[0]}` } }) ``` ### Describe alternatives you've considered I’m considering using **Before Hooks** to handle user creation and generate temporary names as a workaround, but I’m not sure if this is the best approach. I’d like confirmation from others on whether this is the recommended way to handle it for now. ### Additional context In the `phoneNumber` plugin, we can generate temporary user data like: ``` signUpOnVerification: { getTempEmail: (phoneNumber) => `temp-${phoneNumber}@example.com`, getTempName: (phoneNumber) => `User-${phoneNumber.slice(-4)}` } ```
GiteaMirror added the enhancement label 2026-03-13 09:27:13 -05:00
GiteaMirror commented 2026-03-13 09:27:14 -05:00
Author
Owner
Copy Link

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

Hi, @rohityadav-sas. 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 signUpOnVerification feature for the emailOTP plugin, similar to the phoneNumber plugin.
  • The feature would allow automatic user creation with a temporary name after email OTP verification.
  • You proposed including a getTempName function to generate the temporary name.
  • You inquired if using Before Hooks is still the best workaround for this functionality.
  • There has been no further activity or comments on this issue.

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, I will automatically close this issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Jan 9, 2026): Hi, @rohityadav-sas. 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 `signUpOnVerification` feature for the `emailOTP` plugin, similar to the `phoneNumber` plugin. - The feature would allow automatic user creation with a temporary name after email OTP verification. - You proposed including a `getTempName` function to generate the temporary name. - You inquired if using Before Hooks is still the best workaround for this functionality. - There has been no further activity or comments on this issue. **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, I will automatically close this issue. 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
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#2100
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?