refactor(auth)!: authentication is always on; remove FROID_AUTH_ENABLED#97
Merged
Conversation
The HTTP listener now unconditionally requires bearer tokens minted via the Telegram /token command — there is no unauthenticated mode and no way to misconfigure an exposed instance into serving journals openly. The single-tenant router layout and the legacy-database HTTP binding are gone; the default database now only hosts the central token store. FROID_AUTH_ENABLED joins the other removed auth variables as a hard startup error so the change cannot go unnoticed. The Telegram whitelist is now the gate deciding who can mint HTTP credentials, which the README calls out. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
The HTTP listener now unconditionally requires bearer tokens minted via the Telegram /token command — there is no unauthenticated mode and no way to misconfigure an exposed instance into serving journals openly. The single-tenant router layout and the legacy-database HTTP binding are gone; the default database now only hosts the central token store.
FROID_AUTH_ENABLED joins the other removed auth variables as a hard startup error so the change cannot go unnoticed. The Telegram whitelist is now the gate deciding who can mint HTTP credentials, which the README calls out.