502 bad gateway error while using oauth

[DREGALLA]

Before reporting an issue

• [X] I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.

Area

saml

Describe the bug

Hi Team, We have upgraded keycloak to 22.0.4 recently. We are facing 502 bad gateway errors with oauth. It works well without oauth.

1. When we login to workplace with SSO ( Avaya client ), it shows white screen on the first instance and it gives 502 bad gate way error when we try to login again. All subsequent logins give 502 bad gateway error
2. When we login to portal ( Web application with SSO ), we are able to login properly. But when we logout from the same session and try to login again, it gives 502 bad gateway error. If we close the browser and try to login again, it works properly.
3. When we login to outlook plugin with SSO. first login works. But when we reset the application and try to login again, it gives 502 bad gateway error. If we close the app and open again, it works properly.

The customer is using cross domain setup with two IDPS brokers ( "PVP Standardportal" and shibboleth ). We would like to understand if you had observed similar thing for any other customer. Also we need your help on identifying the RCA.

Thank you Dattatreya

Version

22.0.4

Regression

• [ ] The issue is a regression

Expected behavior

User must be able to login properly.

Actual behavior

Users are able to login for the first time. They get 502 bad gateway error if we logout and login again from the same session.

How to Reproduce?

The customer is using cross domain setup with two IDPS brokers ( "PVP Standardportal" and shibboleth ). Please check SSO login multiple times in the same browser session.a

Anything else?

Thank you

[keycloak-github-bot[bot]]

Thanks for reporting this issue, but as this is reported against an older and unsupported release we are not able to evaluate the issue. Please verify with the nightly buildor the latest release.

If the issue can be reproduced in the nightly build or latest release add a comment with additional information, otherwise this issue will be automatically closed within 14 days.

[keycloak-github-bot[bot]]

Due to lack of updates in the last 14 days this issue will be automatically closed.