OIDC behind reverse proxy causes connection loop #1148
Unanswered
baptisterajaut
asked this question in
Q&A
Replies: 1 comment 5 replies
-
the server log would probably tell you what is going on |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello gentlefolks.
I have a particular problem.
I'm supposed to have about 15 differents apache servers behind various oidc configuration, so i built a custom docker image that listens to a full path and manage oidc. This image works flawlessly.
Heres the config :
With this $SubPath variable being the subpath of the domain i use (domain.com/bar/foo being bar/foo as a subpath)
In order to not have 15 different lines on my load balancer, i made a stupid reverse proxy using a server host as subpath
Here's what i mean :
with $Path being in the above example "bar/" so when i access bar/foo i go to a docker container named foo.
This oevrall works but the redirect part is thrown into a loop between the oidc provider and the oidc redirect url (usually bar/foo/redirect_uri )
If i squeeze that "smart" reverse proxy and put directly bar/foo in my load balancer, everything works flwalessly. Liekwise, once i'm logged, that "smart" reverse proxy setup works. But when i want to login using that setup it loops until i get the following error :
the number of existing, valid state cookies (7) has exceeded the limit (7), no additional authorization request + state cookie can be generated, aborting the request
I guess i'm missing something simple but i can't figure it out. Also no help from searching for my issue, and chatgpt is not really of help.
Thanks !
Beta Was this translation helpful? Give feedback.
All reactions