When using Docker, Authentication is usually done in a different container, which then acts as a reverse proxy to the icingaweb docker container. (E.g. using Traefik ForwardAuth)
Apache treats REMOTE_USER as an internal variable that can't be set from the outside (e.g. in the http request from the frontend proxy).
A workaround would be, to set REMOTE_USER to the value of another header, if that exists:
SetEnvIf X-REMOTE-USER "(.*)" REMOTE_USER=$0
This way you can use an external authentication source with the existing docker container.
When using :
icingaweb.authentication.autologin.backend: externalicingaweb expects the user name being in theREMOTE_USERvariable.: https://icinga.com/docs/icinga-web/latest/doc/05-Authentication/#external-authenticationWhen using Docker, Authentication is usually done in a different container, which then acts as a reverse proxy to the icingaweb docker container. (E.g. using Traefik ForwardAuth)
Apache treats
REMOTE_USERas an internal variable that can't be set from the outside (e.g. in the http request from the frontend proxy).A workaround would be, to set
REMOTE_USERto the value of another header, if that exists:This way you can use an external authentication source with the existing docker container.