From 310c5dc09b1ae00373f710a60bb63d59f5c91dbc Mon Sep 17 00:00:00 2001 From: Amir Zarrinkafsh Date: Sun, 3 May 2020 01:10:26 +1000 Subject: [PATCH] [DOCS] Harmonize Remote-User and Remote-Groups headers in nginx example (#963) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fixes #957. Co-authored-by: Clément Michaud --- docs/deployment/supported-proxies/nginx.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/deployment/supported-proxies/nginx.md b/docs/deployment/supported-proxies/nginx.md index dde2815b..e1274679 100644 --- a/docs/deployment/supported-proxies/nginx.md +++ b/docs/deployment/supported-proxies/nginx.md @@ -81,8 +81,8 @@ auth_request_set $target_url $scheme://$http_host$request_uri; # proxy. In the future, it's gonna be safe to just use OAuth. auth_request_set $user $upstream_http_remote_user; auth_request_set $groups $upstream_http_remote_groups; -proxy_set_header X-Forwarded-User $user; -proxy_set_header X-Forwarded-Groups $groups; +proxy_set_header Remote-User $user; +proxy_set_header Remote-Groups $groups; # If Authelia returns 401, then nginx redirects the user to the login portal. # If it returns 200, then the request pass through to the backend. # For other type of errors, nginx will handle them as usual.