Trying to get trusted header auth to work #644
-
Hi, Anyone might know where the problem lies or has already managed to get trusted_header auth working with docker compose? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
Hi @Atlasfreak! Getting these three tools properly hooked up together (in Docker) indeed sounds like a non-trivial endeavor. Just a couple of thought from my side that might help you debug this: First of all, you'll have to set Then, regarding IPs: if you're running Wakapi in Docker, while Apache is running on the host directly, requests relayed from Apache will probably appear to come from the Docker network bridge's gateway address. That's Another issue might be the value that In general, a tool that might help you debug HTTP-related problems like this is https://rbaskets.in/web, I'm using it regularly. Hope that helps. Keep us posted. |
Beta Was this translation helpful? Give feedback.
-
I use kubernetes with Traefik as the reverse proxy, which always gets a variable IP address. I ended up listing all the possible IPs. 😭
Would be great if there was a way to configure subnets in |
Beta Was this translation helpful? Give feedback.
Finally got it to work.
I set the
network_mode
variable tobridge
so that the wakapi container would be attached to the default docker network.Then I could set the
WAKAPI_TRUST_REVERSE_PROXY_IPS
to172.17.0.1
. Additionally I needed to setOIDCAuthNHeader Remote-User
in the apache config.Also you can change the value
mod_auth_openidc
passes to wakapi withOIDCRemoteUserClaim
. I set this tosub
and adjusted the wakapi username to fit the username in authentik.Thanks again for the help @muety rbaskets did really help.
Apparently Apache never sent any Remote-User Header at all not even REMOTE_USER