RPJosh
/
authelia
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[DOCS] Harmonize Remote-User and Remote-Groups headers in nginx example (#963) 

Fixes #957.

Co-authored-by: Clément Michaud <clement.michaud34@gmail.com>
pull/961/head^2
Amir Zarrinkafsh 2020-05-03 01:10:26 +10:00 committed by GitHub
parent d301ebe47c
commit 310c5dc09b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/deployment/supported-proxies/nginx.md
View File

@ -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. # proxy. In the future, it's gonna be safe to just use OAuth.
auth_request_set $user $upstream_http_remote_user; auth_request_set $user $upstream_http_remote_user;
auth_request_set $groups $upstream_http_remote_groups; auth_request_set $groups $upstream_http_remote_groups;
proxy_set_header X-Forwarded-User $user; proxy_set_header Remote-User $user;
proxy_set_header X-Forwarded-Groups $groups; proxy_set_header Remote-Groups $groups;
# If Authelia returns 401, then nginx redirects the user to the login portal. # 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. # If it returns 200, then the request pass through to the backend.
# For other type of errors, nginx will handle them as usual. # For other type of errors, nginx will handle them as usual.