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 #6351] [MERGED] docs: add bearer plugin requirement note to device auth docs #23512

New Issue
Closed
opened 2026-04-15 21:46:50 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-15 21:46:50 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/6351
Author: @GautamBytes
Created: 11/27/2025
Status: ✅ Merged
Merged: 1/6/2026
Merged by: @himself65

Base: canary ← Head: docs/device-auth-bearer-note

📝 Commits (3)

  • a3635cf docs(device-auth): add note about bearer plugin requirement
  • 6e84021 Merge branch 'canary' into docs/device-auth-bearer-note
  • 7d0b664 docs: adjust callout content

📊 Changes

1 file changed (+4 additions, -0 deletions)

View changed files

📝 docs/content/docs/plugins/device-authorization.mdx (+4 -0)

📄 Description

Description

This PR addresses a documentation gap identified in #6348. The Device Authorization documentation provides an example using Authorization: Bearer ${data.access_token}, but previously failed to mention that the Bearer plugin must be enabled in the server configuration for this header to be processed correctly.

I have added a Callout warning in docs/content/docs/plugins/device-authorization.mdx to clarify this prerequisite.

Fixes

Closes #6348

Summary by cubic

Added a warning in the Device Authorization docs that the bearer plugin must be enabled for Authorization: Bearer access tokens (e.g., getSession) to work. Fixes #6348.

Written for commit 7d0b66474f. 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/6351 **Author:** [@GautamBytes](https://github.com/GautamBytes) **Created:** 11/27/2025 **Status:** ✅ Merged **Merged:** 1/6/2026 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `docs/device-auth-bearer-note` --- ### 📝 Commits (3) - [`a3635cf`](https://github.com/better-auth/better-auth/commit/a3635cf3c23e90c509d816e92bebfc3baf9095b6) docs(device-auth): add note about bearer plugin requirement - [`6e84021`](https://github.com/better-auth/better-auth/commit/6e84021ef15bc8ec870cc276152173b22736760f) Merge branch 'canary' into docs/device-auth-bearer-note - [`7d0b664`](https://github.com/better-auth/better-auth/commit/7d0b66474f1bcdf31f69778fe6d03c00fa3cc4a8) docs: adjust callout content ### 📊 Changes **1 file changed** (+4 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/plugins/device-authorization.mdx` (+4 -0) </details> ### 📄 Description ### Description This PR addresses a documentation gap identified in #6348. The Device Authorization documentation provides an example using `Authorization: Bearer ${data.access_token}`, but previously failed to mention that the **Bearer** plugin must be enabled in the server configuration for this header to be processed correctly. I have added a `Callout` warning in `docs/content/docs/plugins/device-authorization.mdx` to clarify this prerequisite. ### Fixes Closes #6348 <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Added a warning in the Device Authorization docs that the bearer plugin must be enabled for Authorization: Bearer access tokens (e.g., getSession) to work. Fixes #6348. <sup>Written for commit 7d0b66474f1bcdf31f69778fe6d03c00fa3cc4a8. 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 21:46:50 -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#23512
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?