Endless loop after Azure AD login #80
Replies: 3 comments 3 replies
-
Once you're redirected back to "signin-oidc", a cookie should be saved in the browser that will allow the session to pass through. What is your app hostname and oidc-guard hostname? Lets say its like this: In this case, you would want the cookieDomain in the helm values to be "domain.com" |
Beta Was this translation helpful? Give feedback.
-
Nginx ingress has a maximum size for the headers which the cookie is a part of, if you look at its logs, you will see that its complaining. You can fix this by updating nginx ingress helm values with the following:
More details, https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#large-client-header-buffers I added some more docs on these issues, https://github.com/IvanJosipovic/OIDC-Guard/wiki/Troubleshooting |
Beta Was this translation helpful? Give feedback.
-
The /userinfo bug is fixed in version 2.3.3 |
Beta Was this translation helpful? Give feedback.
-
Hi,
I get and endless loop after login with Azure AD:
demoapp -> singin -> authorize -> signin-oidc -> demoapp -> singin -> authorize -> signin-oidc -> demoapp
if i look at userinfo everything is there. What can cause that ?
Beta Was this translation helpful? Give feedback.
All reactions