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 #2317] [phone number] Allow for phone verification providers which don't allow OTP customization #9144

New Issue
Closed
opened 2026-04-13 04:30:04 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-04-13 04:30:04 -05:00
Owner
Copy Link

Originally created by @kevcube on GitHub (Apr 16, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/2317

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

I am using Telegram Gateway to verify phone numbers - this platform allows me to send an OTP which is managed by the platform, and allows me to check the user's input against the OTP via API.

The phone number plugin should allow for passing a custom function which sends the OTP, and also passing a custom function which performs validation of the input OTP.

Additionally, telegram gateway will return a request_id which is linked to that OTP, and supports revocation of OTPs.

https://core.telegram.org/gateway/api

Current vs. Expected behavior

current phone number plugin expects the server to set the OTP, when in Telegram Gateway the app's server is never aware of the true OTP. This is also presumably better for security because it limits one way that a backend admin could perform account takeover of a user.

What version of Better Auth are you using?

latest

Provide environment information

- n/a

Which area(s) are affected? (Select all that apply)

Package

Auth config (if applicable)

Additional context

No response

Originally created by @kevcube on GitHub (Apr 16, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/2317 ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce I am using Telegram Gateway to verify phone numbers - this platform allows me to send an OTP which is managed by the platform, and allows me to check the user's input against the OTP via API. The phone number plugin should allow for passing a custom function which sends the OTP, and also passing a custom function which performs validation of the input OTP. Additionally, telegram gateway will return a request_id which is linked to that OTP, and supports revocation of OTPs. https://core.telegram.org/gateway/api ### Current vs. Expected behavior current phone number plugin expects the server to set the OTP, when in Telegram Gateway the app's server is never aware of the true OTP. This is also presumably better for security because it limits one way that a backend admin could perform account takeover of a user. ### What version of Better Auth are you using? latest ### Provide environment information ```bash - n/a ``` ### Which area(s) are affected? (Select all that apply) Package ### Auth config (if applicable) ```typescript ``` ### Additional context _No response_
GiteaMirror added the enhancementlocked labels 2026-04-13 04:30:04 -05:00
GiteaMirror commented 2026-04-13 04:30:07 -05:00
Author
Owner
Copy Link

@catpddo commented on GitHub (Apr 20, 2025):

I noticed that the Telegram Gateway API allows passing a 'code' parameter.
Documentation
The verification code. Use this parameter if you want to set the verification code yourself. Only fully numeric strings between 4 and 8 characters in length are supported. If this parameter is set, code_length is ignored.

Better Auth uses phone number validation and can also use a custom function to send the code.
Documentation

<!-- gh-comment-id:2816963319 --> @catpddo commented on GitHub (Apr 20, 2025): I noticed that the Telegram Gateway API allows passing a 'code' parameter. [Documentation](https://core.telegram.org/gateway/api#sendverificationmessage) `The verification code. Use this parameter if you want to set the verification code yourself. Only fully numeric strings between 4 and 8 characters in length are supported. If this parameter is set, code_length is ignored.` Better Auth uses phone number validation and can also use a custom function to send the code. [Documentation](https://www.better-auth.com/docs/plugins/phone-number#allow-sign-up-with-phone-number)
GiteaMirror commented 2026-04-13 04:30:09 -05:00
Author
Owner
Copy Link

@kevcube commented on GitHub (Apr 20, 2025):

@catpddo you’re right, and I switched to using custom codes. I also use phone verification. But it would still be nice to be able to pass a custom verification function, because I prefer telegram gateway’s method of black-box OTP code sending and verification.

<!-- gh-comment-id:2817063667 --> @kevcube commented on GitHub (Apr 20, 2025): @catpddo you’re right, and I switched to using custom codes. I also use phone verification. But it would still be nice to be able to pass a custom verification function, because I prefer telegram gateway’s method of black-box OTP code sending and verification.
GiteaMirror commented 2026-04-13 04:30:10 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Jul 20, 2025):

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

Issue Summary:

  • You suggested enhancing the phone number plugin to support providers like Telegram Gateway by allowing custom functions for OTP handling.
  • @Catpddo noted that Telegram Gateway API supports custom verification codes and referenced Better Auth's documentation.
  • You acknowledged this but prefer Telegram Gateway's black-box approach for security reasons.
  • @Ninest reacted positively to your comment.

Next Steps:

  • Please confirm if this issue is still relevant to the latest version of the better-auth repository by commenting here.
  • If no updates are provided, the issue will be automatically closed in 7 days.

Thank you for your understanding and contribution!

<!-- gh-comment-id:3094620399 --> @dosubot[bot] commented on GitHub (Jul 20, 2025): Hi, @kevcube. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog. I'm marking this issue as stale. **Issue Summary:** - You suggested enhancing the phone number plugin to support providers like Telegram Gateway by allowing custom functions for OTP handling. - @Catpddo noted that Telegram Gateway API supports custom verification codes and referenced Better Auth's documentation. - You acknowledged this but prefer Telegram Gateway's black-box approach for security reasons. - @Ninest reacted positively to your comment. **Next Steps:** - Please confirm if this issue is still relevant to the latest version of the better-auth repository by commenting here. - If no updates are provided, the issue will be automatically closed in 7 days. Thank you for your understanding and contribution!
GiteaMirror commented 2026-04-13 04:30:11 -05:00
Author
Owner
Copy Link

@Yarmeli commented on GitHub (Jul 24, 2025):

+1

This was also requested a few months ago in #1159 with a fix and a PR attached to it

<!-- gh-comment-id:3111779409 --> @Yarmeli commented on GitHub (Jul 24, 2025): +1 This was also requested a few months ago in #1159 with a fix and a PR attached to it
GiteaMirror commented 2026-04-13 04:30:12 -05:00
Author
Owner
Copy Link

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

Hi, @kevcube. 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 the phone number plugin to support providers like Telegram Gateway that handle OTPs internally, suggesting custom functions for sending and validating OTPs to improve security.
  • A contributor noted Telegram Gateway's API supports custom verification codes and referenced Better Auth's existing documentation.
  • You acknowledged the documentation but expressed a preference for a black-box OTP approach.
  • The issue remains unresolved with interest shown but no implemented solution yet.
  • A related PR was mentioned in issue #1159 by another user.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of better-auth by commenting here to keep the discussion open.
  • Otherwise, this issue will be automatically closed in 7 days.

Thanks for your understanding and contribution!

<!-- gh-comment-id:3437838668 --> @dosubot[bot] commented on GitHub (Oct 23, 2025): Hi, @kevcube. 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 the phone number plugin to support providers like Telegram Gateway that handle OTPs internally, suggesting custom functions for sending and validating OTPs to improve security. - A contributor noted Telegram Gateway's API supports custom verification codes and referenced Better Auth's existing documentation. - You acknowledged the documentation but expressed a preference for a black-box OTP approach. - The issue remains unresolved with interest shown but no implemented solution yet. - A related PR was mentioned in issue #1159 by another user. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of better-auth by commenting here to keep the discussion open. - Otherwise, this issue will be automatically closed in 7 days. Thanks for your understanding and contribution!
GiteaMirror commented 2026-04-13 04:30:13 -05:00
Author
Owner
Copy Link

@kevcube commented on GitHub (Oct 23, 2025):

Not stale afaikOn Oct 24, 2025, at 00:04, dosubot[bot] @.***> wrote:dosubot[bot] left a comment (better-auth/better-auth#2317)
Hi, @kevcube. 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 the phone number plugin to support providers like Telegram Gateway that handle OTPs internally, suggesting custom functions for sending and validating OTPs to improve security.
A contributor noted Telegram Gateway's API supports custom verification codes and referenced Better Auth's existing documentation.
You acknowledged the documentation but expressed a preference for a black-box OTP approach.
The issue remains unresolved with interest shown but no implemented solution yet.
A related PR was mentioned in issue #1159 by another user.

Next Steps:

Please let me know if this issue is still relevant to the latest version of better-auth by commenting here to keep the discussion open.
Otherwise, this issue will be automatically closed in 7 days.

Thanks for your understanding and contribution!

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

<!-- gh-comment-id:3437912003 --> @kevcube commented on GitHub (Oct 23, 2025): Not stale afaikOn Oct 24, 2025, at 00:04, dosubot[bot] ***@***.***> wrote:dosubot[bot] left a comment (better-auth/better-auth#2317) Hi, @kevcube. 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 the phone number plugin to support providers like Telegram Gateway that handle OTPs internally, suggesting custom functions for sending and validating OTPs to improve security. A contributor noted Telegram Gateway's API supports custom verification codes and referenced Better Auth's existing documentation. You acknowledged the documentation but expressed a preference for a black-box OTP approach. The issue remains unresolved with interest shown but no implemented solution yet. A related PR was mentioned in issue #1159 by another user. Next Steps: Please let me know if this issue is still relevant to the latest version of better-auth by commenting here to keep the discussion open. Otherwise, this issue will be automatically closed in 7 days. Thanks for your understanding and contribution! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
GiteaMirror commented 2026-04-13 04:30:14 -05:00
Author
Owner
Copy Link

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

Hi, @kevcube. 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 the phone number plugin to support OTP providers like Telegram Gateway that handle OTPs internally.
  • You suggested adding the ability to pass custom functions for sending and validating OTPs to improve security.
  • A contributor noted Telegram Gateway's API supports custom verification codes and referenced existing documentation.
  • You prefer Telegram's black-box OTP approach over custom verification.
  • The issue remains open with interest from other users and references to related PRs, but no resolution yet.

Next Steps:

  • Please confirm if this issue is still relevant to the latest version of better-auth by commenting here.
  • If no response is received within 7 days, I will automatically close the issue.

Thank you for your understanding and contribution!

<!-- gh-comment-id:3785267817 --> @dosubot[bot] commented on GitHub (Jan 22, 2026): Hi, @kevcube. 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 the phone number plugin to support OTP providers like Telegram Gateway that handle OTPs internally. - You suggested adding the ability to pass custom functions for sending and validating OTPs to improve security. - A contributor noted Telegram Gateway's API supports custom verification codes and referenced existing documentation. - You prefer Telegram's black-box OTP approach over custom verification. - The issue remains open with interest from other users and references to related PRs, but no resolution yet. **Next Steps:** - Please confirm if this issue is still relevant to the latest version of better-auth by commenting here. - If no response is received within 7 days, I will automatically close the 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 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#9144
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?