-
OIDC conf:
This configuration works fine with these browsers: Safari, Firefox & Palemoon However using Chrome in normal mode produces an error consistently:
At first I thought it might have to do with the fact that GitLab has two backend servers, so I configured stick sessions on the fronts (haproxy). I confirmed that the sessions were indeed sticky, yet the problem persists. Also, from reading #683, I tried using:
But found no change in behavior. Can someone provide clues on how to proceed with troubleshooting? Thanks, --C |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
The problem is somewhere with/in the browser, since the backend works with other browsers. Perhaps you can check which User-Agent header the Chrome browser sends in both modes. Also, the full debug log would help more. |
Beta Was this translation helpful? Give feedback.
-
Thanks you @zandbelt . The UA looks the same for both modes:
And the debug logs:
Thanks again, --C |
Beta Was this translation helpful? Give feedback.
-
I set OIDCStateInputHeaders to none and we're golden. Thanks! --Chris |
Beta Was this translation helpful? Give feedback.
I set OIDCStateInputHeaders to none and we're golden.
Thanks!
--Chris