-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get undefined in location URI after Keycloak authentication #79
Comments
Got it, sounds like writing a bug reports help a lot to clarify things :) Traefik must be configured to trust headers from eas (I guess?):
where my containers are started in |
That’s interesting. Keep me in the loop if you see this again as it appears to be an issue with the initial request going down to eas (before the redirect to keycloak). Maybe what you’ve done fully resolves the issue but I find it strange that eas was able to determine part of the request (it clearly properly detected the host for example) but not all of it. In any case thanks for the interest and glad you got it working! Here to help if anything else pops up. |
I can confirm that "trustedIPs" is needed as well when running traefik 2.4 and eas with Google OIDC.
|
Hi @travisghansen,
I'm trying to get eas working in the following architecture (each one are containers):
Here my eas configuration:
The demo backend is declared with following labels in traefik:
And the middleware:
Once I'm logged in keycloak, I'm redirect to
eas.example.com
, and the get a response with following header:I first had a look at #23 but I'm must confess I'm not sure to understand the source issue. As far as I can tell, all users requests received by eas include X-Forward headers (but not in traefik requests to
/verify
off course):Here some eas debug logs where
undefined
appears for the first time:Can you confirm the missing part should be the
requested
URI?Thanks!
The text was updated successfully, but these errors were encountered: