502 Bad Gateway Error with Keycloak as Auth Provider

[leoraba]

Description

When having Stage running behind a reverse proxy like nginx we're getting a 502 Bad Request.
Error is shown after entering valid credentials on Keycloak login page its redirected to stage redirect url showing this error.

However this was temporary solved using the described workaround that is not the final solution.

Workaround

As a temp solution is to adjust ingress to increase proxy buffer size.

nginx.ingress.kubernetes.io/proxy-buffer-size: 32k
nginx.ingress.kubernetes.io/proxy_buffers: 8 16k

solution based on link
Issue related to OHCRN platform issue

Steps to Reproduce

1. Go to stage URL
2. Click on Login Button
3. On Keycloak login page enter valid user credentials
4. Page is redirected to stage redirect URL with the 502 Bad Gateway