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

[GH-ISSUE #6355] Trusted Devices section in 2fa plugin documentation is wrong showing a callbackURL parameter #19125

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

Originally created by @NotCryze on GitHub (Nov 27, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/6355

Is this suited for github?

  • Yes, this is suited for github

To Reproduce

  1. Create an authclient.
  2. Add the 2fa plugin.
  3. Use the authClient.twoFactor.verifyTotp() function.
  4. Try and add a callbackURL which does not exist on the function.
Image

Current vs. Expected behavior

In the docs it is shown as a valid parameter which it is not.
Image

It is also not shown in the actual verifyTotp example.

Image

What version of Better Auth are you using?

1.4.3

System info

N/A

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

Documentation

Auth config (if applicable)

Additional context

No response

Originally created by @NotCryze on GitHub (Nov 27, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/6355 ### Is this suited for github? - [x] Yes, this is suited for github ### To Reproduce 1. Create an authclient. 2. Add the 2fa plugin. 3. Use the `authClient.twoFactor.verifyTotp()` function. 4. Try and add a callbackURL which does not exist on the function. <img width="1461" height="136" alt="Image" src="https://github.com/user-attachments/assets/61047623-1e8b-4380-a795-dfc2947b0112" /> ### Current vs. Expected behavior In the docs it is shown as a valid parameter which it is not. <img width="768" height="301" alt="Image" src="https://github.com/user-attachments/assets/09ba5073-e5f9-4ec0-837b-d2d637cb1cd4" /> It is also not shown in the actual verifyTotp example. <img width="777" height="462" alt="Image" src="https://github.com/user-attachments/assets/16ad0825-f36a-41b5-88be-2846a3c03b56" /> ### What version of Better Auth are you using? 1.4.3 ### System info ```bash N/A ``` ### Which area(s) are affected? (Select all that apply) Documentation ### Auth config (if applicable) ```typescript ``` ### Additional context _No response_
GiteaMirror added the locked label 2026-04-15 17:55:18 -05:00
GiteaMirror commented 2026-04-15 17:55:19 -05:00
Author
Owner
Copy Link

@better-auth-agent[bot] commented on GitHub (Nov 27, 2025):

Thanks for reporting this issue with the Trusted Devices section in our 2FA plugin documentation. It appears that the docs mistakenly show a callbackURL parameter for the authClient.twoFactor.verifyTotp() function, even though the function does not support it. Our team is aware of the discrepancy, and we'll be updating the documentation to remove the incorrect parameter. In the meantime, please adjust your implementation to use only the parameters that are actually supported by the function.

Is there any other part of the 2FA integration or documentation that’s causing confusion for you? Tag @better-auth-agent if you would like an answer from the Agent.

Diagram • Discord • GitHub

Diagram Join Star

<!-- gh-comment-id:3585838183 --> @better-auth-agent[bot] commented on GitHub (Nov 27, 2025): Thanks for reporting this issue with the Trusted Devices section in our 2FA plugin documentation. It appears that the docs mistakenly show a callbackURL parameter for the authClient.twoFactor.verifyTotp() function, even though the function does not support it. Our team is aware of the discrepancy, and we'll be updating the documentation to remove the incorrect parameter. In the meantime, please adjust your implementation to use only the parameters that are actually supported by the function. Is there any other part of the 2FA integration or documentation that’s causing confusion for you? Tag @better-auth-agent if you would like an answer from the Agent. <!-- bot:webhook reply v1 --> [Diagram](https://repodiagrams.s3.eu-north-1.amazonaws.com/better-auth_ultra_detailed_interactive.html) • [Discord](https://discord.gg/better-auth) • [GitHub](https://github.com/better-auth/better-auth) [![Diagram](https://img.shields.io/badge/Diagram-2b3137?style=flat-square)](https://repodiagrams.s3.eu-north-1.amazonaws.com/better-auth_ultra_detailed_interactive.html) [![Join](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&style=flat-square)](https://discord.gg/better-auth) [![Star](https://img.shields.io/badge/star-181717?logo=github&logoColor=white&style=flat-square)](https://github.com/better-auth/better-auth)
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#19125
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?