LAM-1778: Fix stale self-hosted access control docs (Better Auth)#175
Open
laminar-coding-agent[bot] wants to merge 1 commit into
Open
LAM-1778: Fix stale self-hosted access control docs (Better Auth)#175laminar-coding-agent[bot] wants to merge 1 commit into
laminar-coding-agent[bot] wants to merge 1 commit into
Conversation
The allowed-emails.json email allow-list was removed in the NextAuth to Better Auth migration (lmnr #1874). Document the actual current behavior: OAuth provider credentials gate how users sign in, GitHub/Google plus enterprise SSO are supported, and there is no built-in email allow-list. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs Audit (LAM-1778)
Cross-referenced the most recent
lmnrchanges against the docs to find outdated information. One major change found and corrected.🔴 False understanding of self-hosted access control
The Hosting Options page told self-hosters to create an
allowed-emails.jsonfile to restrict access by email. That mechanism (getEmailsConfig) was deleted in the NextAuth → Better Auth migration (lmnr #1874) and has no replacement. Following the old instructions does nothing.Fix: Documented the actual current behavior:
AUTH_GITHUB_*,AUTH_GOOGLE_*) control how users sign in.AUTH_*vars.<Note>clarifies there is no built-in email allow-list: anyone with an account at the configured provider can sign up.All env var names verified against
frontend/lib/auth.tsandfrontend/lib/features/features.tsondev.Verification
grep "—"-> noneallowed-emailsreferences in the docs repoGenerated with Claude Code
Note
Low Risk
Documentation-only change with no runtime or security behavior impact.
Overview
Self-hosted access control on the Hosting Options page is rewritten to match current Better Auth behavior after the NextAuth migration.
The section now explains that instances accept anyone who can reach them by default, and that GitHub/Google (
AUTH_GITHUB_*,AUTH_GOOGLE_*) plus enterprise SSO (Azure Entra ID, Okta, Keycloak viaAUTH_*) control how users sign in. The removedallowed-emails.jsonworkflow and JSON example are gone.A Note states that OAuth does not restrict who can sign up—there is no built-in email allow-list.
Reviewed by Cursor Bugbot for commit c141e0c. Bugbot is set up for automated code reviews on this repo. Configure here.