DISABLE_AUTH env var (single-user / SSO bypass) #705
Someguysomewhere1
started this conversation in
Feature Requests & Ideas
Replies: 3 comments
|
Option B is already present (I have implemented it in one of the earliest PRs to Booklore) grimmory/docs/forward-auth-with-proxy.md Lines 14 to 32 in 4e9cf79 However, right now, it doesn't work anymore (at left for me, I was looking for an issue about that). Upd: created an issue and PR to fix it #388. |
0 replies
|
I'm going to move this to features as if Option B is implemented. Leaving this open for Option A — DISABLE_AUTH environment variable |
0 replies
|
Removed option B from description. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Feature Request: Disable built-in authentication for reverse proxy setups
Use case
Many self-hosted users run Grimmory behind a reverse proxy with authentication already handled at that layer (e.g. Cloudflare Access, Authelia, Authentik, Organizr). In these setups — especially single-user installs — Grimmory's own login page is redundant friction.
Requested feature
One or both of the following:
Option A —
DISABLE_AUTHenvironment variableA simple env var (e.g.
DISABLE_AUTH=true) that skips the login page entirely and grants access as the default/admin user. Similar to how Kavita, Calibre-Web and other self-hosted apps handle this.Why not just use OIDC?
OIDC is great for multi-user setups, but for single-user instances already behind a trusted auth layer, it introduces unnecessary complexity (registering OAuth clients, managing tokens, etc.).
Expected behaviour
DISABLE_AUTH=true: Grimmory loads directly to the main UI, no login promptWorkaround today
None — there is no
DISABLE_AUTHflag, no header trust, and no guest/auto-login mode.All reactions