Hi team, I’m facing issue with my sso (OIDC) configuration I can’t access with my Okta user, only when I’m cleaning the cookies If not - I’m getting

502 bad gateway

nginx error Checking the

ingress-nginx

pods logs, I found the following errors:

2023/02/26 12:47:47 [error] 2331#2331: *16878988 upstream sent too big header while reading response header from upstream, client: <http://xx.xx.xxx.xxx|xx.xx.xxx.xxx>, server: <http://datahub-xxx-xx.xxx.xxx|datahub-xxx-xx.xxx.xxx>, request: "GET /sso HTTP/1.1", upstream: "<http://datahub-xxx-xx.xxx.xxx:9002/sso>", host: "<http://datahub-xxx-xx.xxx.xxx|datahub-xxx-xx.xxx.xxx>", referrer: "<https://datahub-xxx-xx.xxx.xxx/login>"


I0226 14:43:16.410437  66544 request.go:665] Waited for 1.000965907s due to client-side throttling, not priority and fairness, request: GET:<https://xxxxxxxxxxxxx.xxx.us-east-1.eks.amazonaws.com/api/v1/namespaces/ingress-nginx/pods/ingress-nginx-controller-xxxxxxx-xxxx/log?container=controller&follow=true&tailLines=10>

I’ve validate: • DH pods are running • Ingress is configured correct • Services are configured with the right dns & ports •

env | grep AUTH

is configured with the correct values, for

datahub-gms

pod When trying to login with usr+pwd, all works fine I’ve checked with our IT team as well, if the blocker is from our VPN Pls. advise

Hey @powerful-cat-68806, This sounds like nginx buffering configuration issue. Probably the cookies are too big See here how to increase the buffer size: https://ma.ttias.be/nginx-proxy-upstream-sent-big-header-reading-response-header-upstream/

@bulky-electrician-72362 10x HI can I configured it, from the yaml?

Hey, You cannot do it from there. If nginx is not set up by you, ask you k8s admin, to change the confic\

@bulky-electrician-72362 I fixed the annotation, for

values.yaml

, as following:

ingress:
   enabled: true
   annotations:
    <http://kubernetes.io/ingress.class|kubernetes.io/ingress.class>: nginx
    <http://nginx.ingress.kubernetes.io/proxy-buffering|nginx.ingress.kubernetes.io/proxy-buffering>: "off"
    <http://nginx.ingress.kubernetes.io/proxy-buffer-size|nginx.ingress.kubernetes.io/proxy-buffer-size>: "128k"

Issue resolved 10x man 🙂