docs: add proxy configuration security note to access controls - #69
Conversation
Add a caution block explaining that misconfigured reverse proxies (or direct access to tinyauth) can allow users to bypass per-app ACLs by spoofing the X-Forwarded-Host header.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughDocumentation update to the access controls guide adding a caution block about X-Forwarded-Host proxy trust considerations and reverse proxy configuration guidance (nginx) to prevent spoofing, with emphasis that tinyauth should not be directly reachable. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsGit: Failed to clone repository. Please run the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Adds a caution block to the access controls page noting that per-app ACLs depend on the reverse proxy correctly setting
X-Forwarded-Host. If the proxy passes through client-supplied values or tinyauth is directly reachable, users can spoof the header to a non-matching domain and bypass app-level restrictions.The note covers what to check for Traefik, Caddy, and nginx, and recommends keeping tinyauth off the public network.
Summary by CodeRabbit