From c13c0868aebe42c3a5a4b7e5b92c9d7198c302c9 Mon Sep 17 00:00:00 2001 From: oddlama Date: Wed, 21 May 2025 21:15:14 +0200 Subject: [PATCH] docs: document necessity of forwarded-allow-ips with OIDC behind reverse-proxy https (#5461) --- .../docs/documentation/getting-started/authentication/oidc.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/docs/documentation/getting-started/authentication/oidc.md b/docs/docs/documentation/getting-started/authentication/oidc.md index 9eb889f02..5edb1e7b8 100644 --- a/docs/docs/documentation/getting-started/authentication/oidc.md +++ b/docs/docs/documentation/getting-started/authentication/oidc.md @@ -36,6 +36,10 @@ Before you can start using OIDC Authentication, you must first configure a new c http://localhost:9091/login https://mealie.example.com/login + If you are hosting Mealie behind a reverse proxy (nginx, Caddy, ...) to terminate TLS, make sure to start Mealie's Gunicorn server + with `--forwarded-allow-ips=`, otherwise the `X-Forwarded-*` headers will be ignored and the generated OIDC redirect + URI will use the wrong scheme (http instead of https). This will lead to authentication errors with strict OIDC providers. + 3. Configure origins If your identity provider enforces CORS on any endpoints, you will need to specify your Mealie URL as an Allowed Origin.