github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 14:21:55 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #8569] [MERGED] docs: clarify verification storage for OTP flows #24969

New Issue
Closed
opened 2026-04-15 22:39:43 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-15 22:39:43 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/8569
Author: @GautamBytes
Created: 3/12/2026
Status: ✅ Merged
Merged: 3/12/2026
Merged by: @himself65

Base: canary ← Head: docs/update-otp-storage-docs

📝 Commits (2)

  • 533e93f docs: clarify OTP verification storage
  • 2a89580 docs: align secondary storage docs

📊 Changes

5 files changed (+19 additions, -12 deletions)

View changed files

📝 docs/content/docs/concepts/database.mdx (+1 -1)
📝 docs/content/docs/plugins/2fa.mdx (+1 -1)
📝 docs/content/docs/plugins/email-otp.mdx (+3 -3)
📝 docs/content/docs/plugins/magic-link.mdx (+3 -1)
📝 docs/content/docs/reference/options.mdx (+11 -6)

📄 Description

Clarifies that OTP and magic-link flows use Better Auth's shared verification layer, so the storage backend is controlled by the global verification config rather than plugin-specific storage options.

Closes #8542

Changes

  • document verification.storeIdentifier and verification.storeInDatabase in the options reference
  • clarify storeOTP wording in the email OTP docs
  • clarify storeToken wording in the magic link docs
  • clarify storeOTP wording in the 2FA docs
  • fix the verification options example to use a valid field name

Summary by cubic

Clarifies that OTP and magic‑link flows use the shared verification layer, so storage is controlled by the global verification config and secondaryStorage (not plugin options). Documents verification.storeIdentifier/verification.storeInDatabase, updates storeOTP/storeToken wording, notes that verification records default to secondary storage when configured, aligns secondary storage docs, and fixes the verification options example.

Written for commit 2a89580f39. Summary will update on new commits.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/8569 **Author:** [@GautamBytes](https://github.com/GautamBytes) **Created:** 3/12/2026 **Status:** ✅ Merged **Merged:** 3/12/2026 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `docs/update-otp-storage-docs` --- ### 📝 Commits (2) - [`533e93f`](https://github.com/better-auth/better-auth/commit/533e93fb62af42dced2216d17a40d41b6b1abbfb) docs: clarify OTP verification storage - [`2a89580`](https://github.com/better-auth/better-auth/commit/2a89580f39c51ceaef31c65004db60c2075a06ee) docs: align secondary storage docs ### 📊 Changes **5 files changed** (+19 additions, -12 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/concepts/database.mdx` (+1 -1) 📝 `docs/content/docs/plugins/2fa.mdx` (+1 -1) 📝 `docs/content/docs/plugins/email-otp.mdx` (+3 -3) 📝 `docs/content/docs/plugins/magic-link.mdx` (+3 -1) 📝 `docs/content/docs/reference/options.mdx` (+11 -6) </details> ### 📄 Description Clarifies that OTP and magic-link flows use Better Auth's shared verification layer, so the storage backend is controlled by the global `verification` config rather than plugin-specific storage options. Closes #8542 ## Changes - document `verification.storeIdentifier` and `verification.storeInDatabase` in the options reference - clarify `storeOTP` wording in the email OTP docs - clarify `storeToken` wording in the magic link docs - clarify `storeOTP` wording in the 2FA docs - fix the verification options example to use a valid field name <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Clarifies that OTP and magic‑link flows use the shared verification layer, so storage is controlled by the global `verification` config and `secondaryStorage` (not plugin options). Documents `verification.storeIdentifier`/`verification.storeInDatabase`, updates `storeOTP`/`storeToken` wording, notes that verification records default to secondary storage when configured, aligns secondary storage docs, and fixes the verification options example. <sup>Written for commit 2a89580f39c51ceaef31c65004db60c2075a06ee. Summary will update on new commits.</sup> <!-- End of auto-generated description by cubic. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-15 22:39:43 -05:00
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 pull-request
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#24969
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?