Add Security & Authentication page recommending authentik Proxy Provider - #136
Merged
Conversation
Co-authored-by: enoch85 <4511254+enoch85@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add security & authentication page recommending authentik
Add Security & Authentication page recommending authentik Proxy Provider
Aug 4, 2026
… setup, API key description, and checklist Co-authored-by: enoch85 <4511254+enoch85@users.noreply.github.com>
enoch85
marked this pull request as ready for review
August 4, 2026 20:19
…fig link - Move proxy_buffer_size/proxy_buffers into the outpost location where the auth_request subrequest reads the outpost response; keep only proxy_buffering off under location / (proxy_buffers is inert there). - Rotation checklist: drop non-existent "Streamystats credentials" (it stores only a URL and auths with the Jellyfin key), add Sportarr and Tracearr keys. - Add a Traefik forward-auth (single application) example. - Link the Security page from Configuration for publish-online users.
Frame the page as advice for people who want to expose Maintainerr or add a login, not a warning for everyone. Local and VPN-only setups (the common case) need none of it. Rewrite the prose plainly throughout and downgrade the Configuration callout from danger to info.
Drop the repeated reassurances in the exposure lead, the port section bridge, the VPN table row, and the rotation intro. The intro callout is the single source.
Document what Maintainerr actually does to protect data (local-only, no telemetry, verified TLS, log secret-masking, parameterized queries, fail-closed deletes, non-root image) and state plainly that credentials are stored unencrypted at rest. Add an operator hardening checklist.
State plainly that no auth, no rate limiting, and no encryption at rest are deliberate trusted-network-appliance choices, with security expected at the network boundary. Reword the container bullet to factual claims only.
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
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.
Maintainerr has no built-in login. On a private network or over a VPN, which is the most common setup, that is completely fine and needs nothing. But if you want to put it directly on the internet, anyone who can reach it can read your saved credentials (for example
GET /api/settings/database/downloaddownloads the whole database).This PR adds a Security & Authentication page for people in that situation. It is advice for anyone who wants to add a login, not a required setup step. The main suggestion is to put authentik in front of it.
New page:
docs/Security.mdproxy_buffering offunder nginx forward auth, or the page hangs (Maintainerr does not send theX-Accel-Buffering: noheader)Sidebar (
sidebars.js)Added "security" under Getting Started, after "reverseproxy".
docs/API.mdPointed the existing warning at the new page.