From 2c0fa811a21b7ed6203a5aa0dc5c9dc28e82c213 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A9ment=20Michaud?= Date: Mon, 8 Jun 2020 09:17:24 +0200 Subject: [PATCH] [DOCS] Improve documentation around Remote-User and Remote-Groups usage. (#1091) * [DOCS] Improve documentation around Remote-User and Remote-Groups usage. * Update docs/deployment/supported-proxies/index.md Co-authored-by: Amir Zarrinkafsh --- docs/deployment/supported-proxies/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/deployment/supported-proxies/index.md b/docs/deployment/supported-proxies/index.md index 51df1b93..4a5a375a 100644 --- a/docs/deployment/supported-proxies/index.md +++ b/docs/deployment/supported-proxies/index.md @@ -38,7 +38,7 @@ appear in the configuration examples. The only way Authelia can share information about the authenticated user currently is through the use of two HTTP headers: `Remote-User` and `Remote-Groups`. Those headers are returned by Authelia on requests to `/api/verify` and must be forwarded by the reverse proxy to the backends -needing them. +needing them. The headers will be provided with each call to the backend once the user is authenticated. Please note that the backend must support the use of those headers to leverage that information, many backends still don't (and probably won't) support it. However, we are working on solving this issue with OpenID Connect/OAuth2 which is a widely adopted open standard for access delegation.