Troubleshooting

Cookie Auth

Redirect loop after sign-in

If you sign-in and are followed by a redirect loop. For example, demoapp -> singin -> authorize -> signin-oidc -> demoapp -> singin -> authorize -> signin-oidc -> demoapp

This is likely caused by the cookie domain settings.

Lets say that you have a setup like this:
oidc-guard.domain.com
my-app.domain.com

In this case, you would want the settings.cookie.cookieDomain in the Helm values to be "domain.com"

502 Bad Gateway after sign-in

If you sign-in and are followed by a 502 Bad Gateway error, its likely that your cookie is too large to be allowed by Ingress Nginx default settings.

Check the Ingress Nginx logs for more details, if you see the following error, "Request Header Or Cookie Too Large"

You can fix this by updating Ingress Nginx Helm values with the following:

controller:
  config: 
   large-client-header-buffers: 4 16k

More details, https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/configmap/#large-client-header-buffers