Forward Auth Proxy redirects to authentik main page #8756
Replies: 2 comments
-
I've updated the log with a call using a browser without previous session, and I see that there are |
Beta Was this translation helpful? Give feedback.
-
It was definitely a cookie domain problem, and at the same time it highlights a bug in authentik! Cookie domain doesn't allow to specify a port, since they are valid for all the domain, regardless of the port number. But if I don't specify the port number, authentik doesn't match the domain and behaves as I described in the last post. I rebuilt my k3d cluster using port 80 and everything works. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
HI, first of all thanks a ton for this great software! It really will make my life easier when developing my web apps ;)
Unfortunately I incurred in somethink like #1997 : I've setup a Forward Auth proxy for my entire domain, but after the successful authentication it redirects me to the authentik home page.
I'm testing it on k3d (exposed port 50000) using traefik, the middleware is named
authentik
in theauthentik
namespace.Using a whoami example, I defined this ingress:
Enabling the trace log I see that the
X-Forwarded-Host
is there, but it gets lost somewhere.I didn't enable the
allowCrossNamespace
option in traefik, but from what I understand it is only needed if I use theIngressRoute
resource, which is not the case. Or could this be the main culprit?Here's the log:
Beta Was this translation helpful? Give feedback.
All reactions